Datasette 1.0a43 and 0.65.6 ship security fixes
First merged summary.
Datasette 1.0a43 and a 0.65.6 backport close database-download and private-query exposure bugs.
Simon Willison released datasette 1.0a43 and backported a minor security fix to 0.65.6. A database registered with add_database using a route different from its name could be downloaded at /<route>.db by actors who had been denied access. A separate GitHub advisory covers exposure of private stored queries’ titles and SQL without allowing those queries to run. The 1.0a43 release also adds streaming for output renderers, used by built-in TSV and CSV export and available to plugins through Response.stream(). Willison said the 1.0 milestone is 53% complete; the notes do not list earlier affected releases or say whether the issues were used.
- 0.65.6 backports the route-versus-name download fix from 1.0a43.
- Denied actors could fetch /<route>.db when route and name differed.
- Advisory covers private query title and SQL, not execution.
- Built-in TSV and CSV exports now stream every row.
- Plugins can stream rows through Response.stream().
- Willison reports the 1.0 milestone 53% complete.
Timeline
dated events in the reporting · oldest first- Nov 15, 2026Datasette 1.0a43 and 0.65.6 released · Simon Willison
What each outlet adds
beyond the shared facts- Simon Willison0.65.6 backport of the denied /<route>.db download
- Simon Willison1.0a43 streaming, private-query advisory, and 53% milestone
- Products
- datasette
- AI models
- Claude Fable 5.2
Coverage
oldest first · one row per article · UTCDatasette 0.65.6 fixes database download bypass when route differs from name
Denied actors could still fetch /<route>.db when a registered route differed from the database name; the fix came from 1.0a43.
Datasette 1.0a43 fixes leak of private stored query SQL
The issue can reveal a private query’s title and SQL but does not allow that query to run.