Datasette 1.0 alpha series leaks names of databases and tables to unauthenticated users
Medium5.3CVE-2023-40570 · Published Aug 22, 2023 · updated Jun 9, 2026
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| datasette PyPI | >= 1.0a0, < 1.0a4 | 1.0a4 |
Details and references
### Impact This bug affects Datasette instances running a Datasette 1.0 alpha - 1.0a0, 1.0a1, 1.0a2 or 1.0a3 - in an online accessible location but with authentication enabled using a plugin such as [datasette-auth-passwords](https://datasette.io/plugins/datasette-auth-passwords). The `/-/api` API explorer endpoint could reveal the names of both databases and tables - but not their contents - to an unauthenticated user. ### Patches Datasette 1.0a4 has a fix for this issue. ### Workarounds To work around this issue, block all traffic to the `/-/api` endpoint. This can be done with a proxy such as Apache or NGINX, or by installing the [datasette-block](https://datasette.io/plugins/datasette-block) plugin and adding the following configuration to your `metadata.json` or `metadata.yml` file: ```json { "plugins": { "datasette-block": { "prefixes": ["/-/api"] } } } ``` This will block access to the API explorer but will still allow access to the Datasette read or write JSON APIs, as those use different URL patterns within the Datasette `/database` hierarchy.
More datasette advisories
All| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Jun 72021 | Reflected cross-site scripting issue in Datasette CVE-2021-32670Medium7.2fixed in 0.56.1 | Medium7.2 | 0.56.1 |
| Nov 62025 | Open redirect endpoint in Datasette CVE-2025-64481Lowfixed in 0.65.2, 1.0a21 | Low | 0.65.2, 1.0a21 |
| Aug 112020 | CSRF tokens leaked in URL by canned query form GHSA-q6j3-c4wc-63vwMedium4.3fixed in 0.46 | Medium4.3 | 0.46 |