Release: datasette 1.0a40
Same security fix as 0.65.5, plus some neat new features and bug fixes:
datasette.client.get() method.
Release: datasette 0.65.5
Security fix for an issue where a trailing newline in a requested table name could bypass table permissions and expose private rows, reported by dpfkdlemtp in GHSA-h547-rmjf-5m2m.
Datasette 1.0a39 and 0.65.4 security releases
Today we're releasing two new security patch versions of Datasette: 1.0a39 and 0.65.4 - one for the current alpha series and one for the stable 0.65.x family.These are security fixes which you should apply if you are running a Datasette instance on the public web - in particular if that instance mixes both public and private tables.
Following issues reported by Sevban Dönmez, Alex Garcia and I ran an extensive audit of Datasette using Claude Fable 5.1, GPT-5.6, and GPT-6 Astra. We then spent almost a week collaborating on and reviewing the fixes.
They helped find some very subtle bugs. We'll be incorporating security audits by frontier models into all of our development work going forward.
Alex came up with a way of splitting the work which I found extremely productive:
Alex Garcia and I worked together running and then responding to the audit, working in a shared private repository. For most of the issues we split the work: one of us would create the automated tests highlighting the issue, then the other would implement the fix. This ensured that two separate humans had eyes on each of the issues, in addition to our coding agents running different models.
Tags: releases, security, ai, datasette, generative-ai, llms, agentic-engineering, ai-security-research
Release: datasette 0.65.4
See Datasette 1.0a39 and 0.65.4 security releases on the Datasette blog.
Release: datasette 1.0a39
See Datasette 1.0a39 and 0.65.4 security releases on the Datasette blog.
