Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The turso-cli package, versions before 1.0.26, saves the user's Turso platform JWT to settings.json with mode 0o644, so other local users on the same system can read it. A local user or process on the host can read the token and gain full Turso platform access for the user's organizations, including creating or destroying databases and changing billing. Upgrade to turso-cli 1.0.26, which fixes the issue; until then, tighten the settings file permissions manually, and repeat this after commands that recreate the file such as turso auth login.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.5 | Medium | 3.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0015, the 4th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:05 UTC First seen by agentprime
- 31 Oct 2026, 15:05 UTC Confirmed by OSV