International
The Morning Dev

Only the news worth knowing

‹
 
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

  1. 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
YesHits tech teamsJudgment: Datasette is an open-source data-publishing server that developers and data teams run.
NoCore infrastructureJudgment: Datasette is a single application, not software nearly every team runs.
NoPopular toolJudgment: Datasette is a niche data tool, not mainstream developer tech.
NoExploited in the wildSimon Willison's Weblog: the release notes describe a fixed security issue; no observed attacks are reported.
NoPublic exploitSimon Willison's Weblog: only a fix and description are given; no exploit code or PoC is mentioned.
NoRemote, no loginSimon Willison's Weblog: downloads by actors denied access; the sources do not say no credentials are needed.
NoFull takeoverSimon Willison's Weblog: the flaw allowed database downloads, which is information disclosure, not code execution or admin takeover.
NoSecrets exposedSimon Willison's Weblog: the flaw could allow downloads; no source reports data was actually stolen or exposed.
NoSupply chainSimon Willison's Weblog: a normal access-control bug fix; no malicious code shipped through a trusted channel.
NoNo fix yetSimon Willison's Weblog: the fix is released in datasette 1.0a43 and backported in 0.65.6.

Timeline

  1. Datasette 1.0a43 and 0.65.6 released, with the security fix backported to 0.65.6

  2. Simon Willison's Weblog

    datasette 0.65.6

  3. Simon Willison's Weblog

    datasette 1.0a43

Full coverage · 2 sources

First seen · 2 sources · Full story page · How tiers are decided