Platform token disclosure via world-readable settings file
Published Aug 11, 2026 · Updated Aug 11, 2026
Incorrect file permissions in Turso CLI before 1.0.26 allow local users to read a stored platform JWT from settings.json. The settings persistence path passes the JWT to Viper's WriteConfig without overriding its default 0644 mode, so settings.json is created world-readable. Another local UID on a Linux or macOS host can recover the token and access the user's Turso organizations, databases, data, credentials, and billing settings.
Summary
What happened
Incorrect file permissions in Turso CLI before 1.0.26 allow local users to read a stored platform JWT from settings.json. The settings persistence path passes the JWT to Viper's WriteConfig without overriding its default 0644 mode, so settings.json is created world-readable. Another local UID on a Linux or macOS host can recover the token and access the user's Turso organizations, databases, data, credentials, and billing settings.
The record
- CVE
- CVE-2026-48790
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Turso
- Product
- Turso CLI
- Classifications
- CWE-732, CWE-276, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.26
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Viper settings-permission reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo