Datasette 0.65.4 Security Update: Stable Branch Backport Patches Vulnerability

Datasette 0.65.4 delivers a security backport to the stable branch alongside the 1.0a39 alpha release.
Datasette has released version 0.65.4, a security-focused maintenance update shipping alongside 1.0a39. The project uses a dual-track strategy — backporting security fixes to the stable 0.65.x branch while the 1.0 alpha explores new features — ensuring users not yet ready to migrate still receive protection. Since Datasette exposes SQLite databases as queryable web services, security flaws carry direct data exposure risks, making prompt upgrades essential for publicly accessible instances.
Datasette Releases Security Update
Datasette, the open-source data exploration and publishing tool, has released version 0.65.4 — a maintenance release focused entirely on security fixes. The update ships alongside version 1.0a39, with both branches updated simultaneously, indicating that this fix covers multiple version lines currently under active maintenance.
According to release notes published by project author Simon Willison on the official Datasette blog, this is a security release. For Datasette instances running in production environments that expose data query interfaces to the public, this type of update is generally recommended to be applied as soon as possible to prevent potential vulnerabilities from being exploited.

Why the 0.65.x Branch Is Still Being Maintained
Datasette is currently in the process of transitioning to a stable 1.0 release, with the 1.0 series continuing to iterate through alpha versions (such as 1.0a39). At the same time, 0.65.x remains an actively maintained stable branch — and this 0.65.4 release is a security backport targeting that branch.
This dual-track maintenance strategy — where a newer version explores cutting-edge features while the older stable version continues to receive security patches — is common practice among mature open-source projects. The benefit is clear: users who aren't yet ready to migrate to the 1.0 alpha can still receive security coverage on the familiar 0.65 branch, without being forced to upgrade to a pre-release version where features are still in flux.
Recommendations for Users
For developers and data teams currently deploying Datasette, here are some practical steps to take when faced with this kind of security release:
- First confirm which version branch you're running, then determine whether you should upgrade to 0.65.4 or 1.0a39.
- Read the official blog's security notes to understand the scope of the vulnerability and whether it affects publicly exposed instances.
- If you're using Datasette to expose a database for public querying over the internet, treat this upgrade as a higher priority.
Datasette's core value proposition is turning any SQLite database into a browsable, queryable, API-accessible online service — which means security has a direct bearing on the exposure risk of your underlying data. Staying on top of security releases is an essential habit when using tools like this.
Summary
0.65.4 is not a major feature release, but as a security fix it reflects the Datasette project's ongoing commitment to users on the stable branch. Affected users are encouraged to review the official release notes, assess whether an upgrade is necessary, and apply the update promptly.
Related articles

Vercel AI SDK Releases Vue 3.0.282 Patch Update
Vercel AI SDK releases @ai-sdk/vue@3.0.282 patch update, syncing with core package ai@6.0.282. Learn about the changes, release cadence, and upgrade recommendations.

Vercel AI SDK Sandbox Component Receives Patch Update
Vercel AI SDK releases sandbox-vercel@1.0.109 patch update, syncing the harness dependency to the same version. A look at this maintenance release and what it means for AI app developers.

Vercel AI SDK Vue 4.0.99 Released: Dependency Update Overview
The @ai-sdk/vue 4.0.99 patch release syncs the underlying ai@7.0.99 dependency. Learn what this means for Vue developers building AI apps with Vercel AI SDK.