SecurityFan score 20 · Tier C2 sources
datasette 0.65.6
The Brief · written from 2 sources
- 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.
Who’s affected
- Datasette users who register databases with custom routes via add_database
What to do
- Upgrade to Datasette 1.0a43 or Datasette 0.65.6
- Datasette 1.0a43
- Datasette 0.65.6
- #datasette
- #security
- #access-control
- #release
- #python
Release: datasette 0.65.6 I backported a minor security fix from 1.0a43: Fixed a security issue where a database registered using add_database(db, name=..., route=...) with a route that differs from its name could be downloaded from /<route>.db by actors who were denied access to…
Timeline
Full coverage · 2 sources
- 2d ago ↗
Simon Willison's Weblog
datasette 1.0a43 - 2d ago ↗
Simon Willison's Weblog
datasette 0.65.6