Datasette 1.0a43: Private Stored-Query Leak Fixed, Streaming Exports Ship Datasette 1.0a43 shipped on November 15, 2026, fixing a private stored-query metadata exposure that let unauthorized actors read the title and SQL text of private queries, alongside a database download ACL bug fixed in both 1.0a43 and the 0.65.6 stable line. Simon Willison, Datasette's creator, said the stored-query flaw was worthy of a published GitHub advisory, and the release also adds a Response.stream() feature flag so built-in CSV and TSV exporters stream row batches instead of buffering whole tables in memory. Willison put the 1.0 milestone at 53% complete, with heavy use of Claude Fable 5.2, and companion plugins datasette-agent 0.6.0, datasette-apps 0.4.0 and datasette-maplibre 0.1a0 shipped the same weekend. Datasette 1.0a43 arrived on November 15, 2026 with a security fix for private stored queries , streaming CSV and TSV exports, and a pile of 1.0 milestone polish—while companion plugins datasette-agent 0.6.0 , datasette-apps 0.4.0 , and datasette-maplibre 0.1a0 shipped the same weekend. Datasette.io's news post https://datasette.io/news/2026-11-15?ref=explainx is the authoritative changelog; Simon Willison's release write-up https://simonwillison.net/2026/Nov/15/datasette/?ref=explainx adds context on Claude Fable 5.2 assisting the 1.0 push. If you publish SQLite to the web for newsrooms, NGOs, or internal ops dashboards, this release is both patch Tuesday and feature Friday : close ACL leaks before agents get wider store-query permissions https://explainx.ai/blog/llm-0-37-simon-willison-gpt-6-1-sol-terra-openai-compatible-endpoint-add-guide-2026 , then turn on streaming exports so million-row tables do not OOM your workers. TL;DR | Item | Detail | |---|---| | Versions | 1.0a43 1.0 alpha and 0.65.6 0.6 stable | | Security | Private stored-query metadata exposure fixed in 1.0a43; database download ACL fix in both lines | | Advisory | Willison deemed the stored-query issue GitHub advisory–worthy see the Datasette security advisories page https://github.com/simonw/datasette/security/advisories?ref=explainx | | Feature flag | Response.stream for output renderers; core CSV/TSV use it | | Agent UX | datasette-agent 0.6 homepage prompt + table hash-mentions | | Apps | datasette-apps 0.4 URL fragments for cross-app linking | | Maps | datasette-maplibre 0.1a0 MapLibre + OpenFreeMap plugin | | 1.0 progress | Willison: milestone 53% complete, heavy Claude Fable 5.2 use | Security: private stored queries and database downloads Datasette.io https://datasette.io/news/2026-11-15?ref=explainx summarizes two classes of bugs: 1. Private stored queries — actors who should not see a private query could still read title and SQL text , even if they could not execute it. That is a confidentiality breach for teams using stored queries as saved investigation playbooks. 2. Database downloads — when a database is registered under a route different from its filename , download ACLs could let denied actors fetch the file anyway. Willison's personal release notes https://simonwillison.net/2026/Nov/15/datasette/?ref=explainx say one flaw deserved a published GitHub advisory . Multi-tenant instances—common in data journalism circles that adopted Datasette during COVID dashboards—should treat this as patch-now , not next sprint. A protected key in a capsule evoking private stored-query metadata patched in Datasette 1.0a43 Upgrade matrix | Track | Version | Action | |---|---|---| | Running 1.0 alphas | → 1.0a43 | pip install datasette==1.0a43 | | Running 0.6x stable | → 0.65.6 | Same pin on 0.65.6 | | Private queries unused | Still upgrade | Download ACL bug may still apply | | Air-gapped single-user | Lower urgency | Metadata leak risk minimal | After upgrading, audit view-query , store-query , and download-database permissions on each published database. The stored-query redesign from 1.0a31 https://explainx.ai/blog/mcp-2026-07-28-stateless-spec-july-2026 made queries first-class rows; this patch closes a hole in that model. Adapter pipes meeting through a junction evoking Datasette streaming CSV and TSV export renderers Streaming exports and the 1.0 finishing list The headline feature is Response.stream for output renderers . Built-in TSV and CSV exporters now stream row batches instead of buffering entire tables in memory—critical when reporters dump multi-gigabyte public-records tables. Plugins can register as stream-capable , which matters for bespoke redacted exports in legal-tech stacks. Willison also shipped: - Row JSON layout deemed ready for 1.0 freeze. -