Vulnerability in github.com/tursodatabase/turso-cli (CVE-2026-48790)
Summary
Vulnerability in github.com/tursodatabase/turso-cli (CVE-2026-48790). Confidential information can be exposed externally. Exploitable via configPermissions. Mitigation: upgrade to 1.0.26 or later.
Original description
The description as published by the source.
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 - Linux:
~/.config/turso/settings.json(or$XDG_CONFIG_HOME/turso/settings.json)
It contains the platform JWT in plaintext JSON alongside organization and username fields.
Comparable CLIs (gh, aws, docker, gcloud, plus close peers planetscale, neon, upstash) write credential files at 0o600 explicitly, so this is a deviation from the cross-vendor baseline rather than a deliberate trade-off.
Details
The OAuth callback handler stores the pl…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48790 has been found in github.com/tursodatabase/turso-cli.
Attackers can target a specific entry point like configPermissions over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade github.com/tursodatabase/turso-cli to 1.0.26 or later.
If unsure, ask your IT team or search "github.com/tursodatabase/turso-cli CVE-2026-48790" on the vendor's site.
CVE-2026-48790 (github.com/tursodatabase/turso-cli) — CWE-276 / CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: configPermissions / organization / username / aws
Patched: 1.0.26 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-276) exists in github.com/tursodatabase/turso-cli. Attackers reach the vulnerable code path via configPermissions.
Check the vendor advisory for the affected versions of github.com/tursodatabase/turso-cli. Attack surface: configPermissions / organization / username / aws.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to 1.0.26.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/tursodatabase/turso-cli' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/tursodatabase/turso-cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/tursodatabase/turso-cliを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/tursodatabase/turso-cli to 1.0.26ステージング環境で 1.0.26 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。