DigestAI news desk
● OpenAI board member warns company is not on track to prevent catastrophic AI loss of control ● OpenAI launches Agents API beta for long-running cloud agents ● OpenAI solves Navier-Stokes problem, sparking academic controversy over data use ● RTK Token Savings Debunked: Cost Benchmarks Disagree ● The Waymo effect: AI making research less collaborative ● Meta’s Muse AI Agent Seeks User Trust with Secure Architecture ● Thelio Mira AI Linux Workstation with 192 GB GPU Memory ● Claude No Longer Available to Minors
Generative AI & Models updated 1 min read

Datasette Security Patches Released

On September 11, 2026, Datasette, a database server, released two security patches: 1.0a39 and 0.65.4. These updates address vulnerabilities found through an extensive security audit conducted by Claude Fable 5.1, GPT-5.6, and GPT-6 Astra. The audit was initiated after reports of security issues. The team, led by Alex Garcia, collaborated closely with Simon Willison on the fixes. The process…

1 source

Key points

  • Datasette released security patches 1.0a39 and 0.65.4
  • Audit conducted by Claude Fable 5.1, GPT-5.6, and GPT-6 Astra
  • Fixes address vulnerabilities found in the database server
Full story from Simon Willison · by Simon Willison Open source ↗

Datasette 1.0a39 and 0.65.4 security releases

Simon Willison · 11 September 2026

11th September 2026 - Link Blog

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.

Recent articles

  • Some thoughts on the Navier–Stokes Millennium Prize Problem - 8th September 2026
  • The Pelican comparison grid for Astra is pretty interesting - 4th September 2026
  • OpenAI's rogue agents were caught communicating via public wikis - 4th September 2026

This text was published by Simon Willison and written by Simon Willison. It is reproduced here with attribution so you can read it in full; the rights remain with the publisher. Read it at the source ↗

Topics · follow one to build your own front page
DatasetteClaude Fable 5.1GPT-5.6GPT-6 AstraSimon WillisonAlex Garcia

The headline, key points and digest above were generated by Digest AI's editorial model from the linked sources. Automated summaries can contain errors: the sources are the record. Spotted a mistake? Tell us.

Comments

via GitHub Discussions

Related stories