C20/100
Vulnerability · low
Datasette 1.0a43 and 0.65.6 release a backported security fix
Tier C · Keep an eye on it – Check if you’re affected
Who’s exposed: Datasette instances registering databases with routes that differ from names
Tier C because: Hits tech teams
Reach
Attack
Damage
Fix
What to do
- Upgrade to Datasette 1.0a43 or Datasette 0.65.6
The Brief
- Datasette 1.0a43 and 0.65.6 were released on 2026-11-15, with 0.65.6 backporting a security fix from 1.0a43.
- The fix addresses a database registered with add_database(db, name=..., route=...) where the route differs from the name, which could be downloaded from /<route>.db by actors denied access to it.
- The 1.0a43 release also adds streaming support for output renderers, with the built-in TSV and CSV exports now using it.
Why it matters
If you register Datasette databases with a route that differs from their name, actors without access to a database could previously download it, so upgrading closes an access-control gap.
The checklist behind the tier
Checklist · 1 of 10 yes
| Yes | Hits tech teams | Judgment: Datasette is an open-source data-publishing server that developers and data teams run. |
| No | Core infrastructure | Judgment: Datasette is a single application, not software nearly every team runs. |
| No | Popular tool | Judgment: Datasette is a niche data tool, not mainstream developer tech. |
| No | Exploited in the wild | Simon Willison's Weblog: the release notes describe a fixed security issue; no observed attacks are reported. |
| No | Public exploit | Simon Willison's Weblog: only a fix and description are given; no exploit code or PoC is mentioned. |
| No | Remote, no login | Simon Willison's Weblog: downloads by actors denied access; the sources do not say no credentials are needed. |
| No | Full takeover | Simon Willison's Weblog: the flaw allowed database downloads, which is information disclosure, not code execution or admin takeover. |
| No | Secrets exposed | Simon Willison's Weblog: the flaw could allow downloads; no source reports data was actually stolen or exposed. |
| No | Supply chain | Simon Willison's Weblog: a normal access-control bug fix; no malicious code shipped through a trusted channel. |
| No | No fix yet | Simon Willison's Weblog: the fix is released in datasette 1.0a43 and backported in 0.65.6. |
Timeline
Full coverage · 2 sources
- 2d ago ↗
Simon Willison's Weblog
datasette 1.0a43 - 2d ago ↗
Simon Willison's Weblog
datasette 0.65.6
First seen · 2 sources · Full story page · How tiers are decided