Skip to content
NewA calmer, faster ZeroHour

Datasette 1.0a43 fixes leak of private stored query SQL

Original title: datasette 1.0a43

Simon Willison ()1
Part of a story covered by 2 sourcesDatasette 1.0a43 and 0.65.6 ship security fixesMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

The issue can reveal a private query’s title and SQL but does not allow that query to run.

Simon Willison released datasette 1.0a43 and said the 1.0 milestone is 53% complete. The main 1.0 change is streaming for output renderers, now used by built-in TSV and CSV export and available to plugins through Response.stream(). The release also includes security fixes, including a GitHub advisory for exposure of private stored queries’ titles and SQL without allowing execution.

Unconfirmed: The post is truncated, so the other security fix and remaining changes are not fully described.

Key facts
  • The 1.0 milestone is reported 53% complete.
  • Plugins can stream every row via Response.stream().
  • Built-in TSV and CSV exports now stream.
  • The advisory covers title and SQL, not execution.
  • He used Claude Fable 5.2 while working toward 1.0.
Security assessment · AI, from the article

Impact: private stored query titles and SQL exposed

ProductAffectedFixed in
datasette—1.0a43
What to do
  1. 1.Upgrade to datasette 1.0a43
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

Release: datasette 1. 0a43 I've been leaning hard into Claude Fable 5. 2 to help knock things off the 1.

Simon Willison

simonwillison.net

Read the full article at Simon Willison

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.