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

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

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-57f6-pvx8-hwj6, GO-2026-5811

## 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 (Incorrect Permission Assignment for Critical Resource), CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2026-48790?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/tursodatabase/turso-cli` | Go | All versions | 1.0.26 |
| `github.com/tursodatabase/turso-cli` | Go | All versions | 1.0.26 |
| `github.com/tursodatabase/turso-cli` | Go | All versions | 1.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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48790 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-48790 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/tursodatabase/turso-cli (Go): affected all versions; fixed in 1.0.26
- github.com/tursodatabase/turso-cli (Go): affected all versions; fixed in 1.0.26
- github.com/tursodatabase/turso-cli (Go): affected all versions; fixed in 1.0.26

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48790/ (Markdown: https://insights.sbomify.com/CVE-2026-48790/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48790
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48790
- OSV: https://osv.dev/vulnerability/CVE-2026-48790

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48790/
Summaries are generated and may contain mistakes; the official description above is the record.