CVE-2026-48790 turso-cli persists Turso platform JWT with world-readable (0o644) file permissions

Medium 5.5 Published Updated

Local attackers can read world-readable JWT credentials from Turso CLI settings, enabling unauthorized access to the user's Turso platform account.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-48790?

CVE-2026-48790 is a medium-severity vulnerability in tursodatabase turso-cli, published on 11 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

Turso CLI is the command line interface (CLI) to the open-source database Turso. Versions prior to 1.0.26 persist the user's Turso platform JWT to `settings.json` using Viper's default `configPermissions` of `0o644`, leaving the credential file world-readable on standard Linux and macOS systems. Any other local UID on the host can read the file and recover the platform JWT, which grants full Turso platform access scoped to the user's organizations. Version 1.0.26 patches the issue.

Weakness: CWE-732, CWE-276

Which versions are affected by CVE-2026-48790?

3 open source packages ship an affected version, including github.com/tursodatabase/turso-cli.

PackageAffectedFixed in
github.com/tursodatabase/turso-cli GoAll versions1.0.26
github.com/tursodatabase/turso-cli GoAll versions1.0.26
github.com/tursodatabase/turso-cli GoAll versions1.0.26

How do I fix CVE-2026-48790?

Upgrade github.com/tursodatabase/turso-cli to 1.0.26 or later.

Is CVE-2026-48790 being exploited?

There is no known exploitation of CVE-2026-48790 in the wild and no public exploit code.

Sources

Also known as GHSA-57f6-pvx8-hwj6, GO-2026-5811.

Is CVE-2026-48790 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free