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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-48790: 0.15% estimated exploitation activity in the next 30 days; percentile 4.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary turso-cli persists 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. Impact The token in settings.json grants the holder full Turso platform access — create or destroy databases, rotate credentials, exfiltrate data, change billing settings — for any organization the user belongs to. Because the file is world-readable, the credential is reachable by: - Cron jobs or daemons running as a different system user on the same host - Sandboxed CI runners with a mounted home directory - Containers with a bind-mounted host home - Co-tenants on a shared multi-user developer or jumpbox host The file path resolves through configdir.LocalConfig("turso"): - macOS: ~/Library/Application Support/turso/settings.json…

Published by the source

26 Jun 2026, 20:44 UTC

Last modified by the source

26 Jun 2026, 20:44 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-57f6-pvx8-hwj6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-48790

Advisory: turso-cli persists Turso platform JWT with world-readable (0o644) file permissions
IDs: CVE-2026-48790, GHSA-57f6-pvx8-hwj6
Record: https://patchnext.com/advisories/cve-2026-48790 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/tursodatabase/turso-cli 1.0.26. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/tursodatabase/turso-cli: affected <= 1.0.25; fixed in 1.0.26

## Suggested inspection (read-only)
- Go github.com/tursodatabase/turso-cli: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/tursodatabase/turso-cli.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-57f6-pvx8-hwj6 (GitHub-reviewed advisory GHSA-57f6-pvx8-hwj6 lists affected ranges: Go github.com/tursodatabase/turso-cli >=0 <=1.0.25)

Commands are suggestions: review each one before running it.