CVE-2026-48790
Received Received - Intake

Turso CLI JWT Exposure via Insecure File Permissions

Vulnerability report for CVE-2026-48790, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-11

Last updated on: 2026-08-11

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-11
Last Modified
2026-08-11
Generated
2026-08-11
AI Q&A
2026-08-11
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
turso cli to 1.0.26 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-732 The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
CWE-276 During installation, installed file permissions are set to allow anyone to modify those files.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Turso CLI versions before 1.0.26 store the user's Turso platform JWT in a settings.json file with overly permissive permissions (0o644). This allows any local user on the system to read the token, potentially granting unauthorized access to the user's Turso platform account.

Detection Guidance

Check if the settings.json file in the Turso CLI configuration directory has overly permissive settings. Run: ls -l ~/.turso/settings.json to verify permissions. If permissions show 644 or similar, the file is world-readable and vulnerable.

Impact Analysis

An attacker with local access could read the JWT token and perform actions like creating databases, rotating credentials, exfiltrating data, or modifying billing across all organizations the user belongs to.

Mitigation Strategies

Upgrade to Turso CLI version 1.0.26 or later. If unable to upgrade, manually set restrictive permissions on the settings.json file and its directory using: chmod 600 ~/.turso/settings.json and chmod 700 ~/.turso.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48790. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart