Datasette ships two rounds of security releases: 1.0a39/0.65.4, then 0.65.5/1.0a40 for public/private table permission flaws

Datasette issued coordinated security releases for its 1.0 alpha series and stable 0.x branch: 1.0a39 and 0.65.4 (2026-09-11) fixed subtle bugs affecting instances that mix public and private tables, found via an AI-assisted audit, and follow-ups 0.65.5 and…

Datasette, the open-source data exploration tool, published parallel security patches for both release lines. On 2026-09-11 it shipped 1.0a39 (1.0 alpha series) and 0.65.4 (stable 0.65.x/0.x line), fixing subtle bugs affecting instances that mix public and private tables, with public-web instances the priority for patching. The issues were reported by Sevban Dönmez and Alex Garcia, after which the maintainers conducted an extensive audit of the codebase using the frontier models Claude Fable 5.1, GPT-5.6, and GPT-6 Astra; fixes were developed and reviewed collaboratively over nearly a week. That announcement assigned no CVE identifiers and reported no in-the-wild exploitation, and suggested frontier-model security audits will become standard practice. On 2026-09-16, follow-up releases 0.65.5 (stable) and 1.0a40 (alpha) fixed a flaw tracked as GHSA-h547-rmjf-5m2m, reported by dpfkdlemtp, in which a trailing newline in a requested table name bypassed table permission checks and could expose private rows; the reports do not explicitly state whether this advisory corresponds to any of the issues behind the earlier wave. The 1.0a40 alpha also adds a datasette.add_background_task() method letting plugins launch and manage background tasks, migrates internal client methods such as datasette.client.get() to httpx2, and includes bug fixes from issue triage ahead of a stable 1.0.