CVE-2026-48790

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 26, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 12, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

turso-cli persists Turso platform JWT with world-readable (0o644) file permissions · Advisory · tursodatabase/turso-cli · GitHub

https://github.com/tursodatabase/turso-cli/security/advisories/GHSA-57f6-pvx8-hwj6
GitHub commit

commit ffb914849216 (tursodatabase/turso-cli)

Fix landed in tursodatabase/turso-cli commit ffb914849216 — awaiting tagged release

https://github.com/tursodatabase/turso-cli/commit/ffb914849216ef5a86353b3fa6cee66f33af3b66
Web page

viper/viper.go at v1.21.0 · spf13/viper · GitHub

https://github.com/spf13/viper/blob/v1.21.0/viper.go#L198
Web page

viper/viper.go at v1.21.0 · spf13/viper · GitHub

https://github.com/spf13/viper/blob/v1.21.0/viper.go#L1688

Vendor Advisories for CVE-2026-48790(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/tursodatabase/turso-cli—
  • every version up to 1.0.26: fixed in 1.0.26
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 24× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-11 19:43 UTCEG score recompute
  2. 2026-10-11 16:58 UTCEG score recompute
  3. 2026-10-11 14:22 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-09-23 07:48 UTCEG score recompute
  21. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-09-18 07:11 UTCEG score recompute
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-09-12 15:33 UTCEG score recompute
  25. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
Show 42 more
  1. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-09-09 22:59 UTCEG score recompute
  3. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-09-06 15:59 UTCEG score recompute
  6. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-08-30 19:20 UTCEG score recompute
  10. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-08-27 23:01 UTCEG score recompute
  14. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-08-24 12:52 UTCEG score recompute
  17. 2026-08-23 08:31 UTCEG score recompute
  18. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-08-22 09:24 UTCEG score recompute
  20. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-08-21 05:28 UTCEG score recompute
  22. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-08-18 23:42 UTCEG score recompute
  24. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-08-17 16:59 UTCEG score recompute
  26. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  27. 2026-08-16 18:17 UTCEG score recompute
  28. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  29. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  30. 2026-08-15 19:30 UTCEG score recompute
  31. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  32. 2026-08-13 22:04 UTCEG score recompute
  33. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  34. 2026-08-12 23:22 UTCEG score recompute
  35. 2026-08-12 22:21 UTCEG score recompute
  36. 2026-08-12 17:22 UTCEG score recompute
  37. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  38. 2026-08-11 18:40 UTCEG score recompute
  39. 2026-07-30 13:21 UTCEG score recompute
  40. 2026-07-26 14:31 UTCEG score recompute
  41. 2026-07-23 03:18 UTCEG score recompute
  42. 2026-06-26 21:41 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48790?
CVE-2026-48790 is a medium-severity vulnerability; its CVE record was published on June 26, 2026. 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…
When was the CVE record for CVE-2026-48790 published?
The CVE record for CVE-2026-48790 was published on June 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-48790 actively exploited?
CVE-2026-48790 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48790?
CVE-2026-48790 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48790?
A fix for CVE-2026-48790 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48790 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48790

Explore →

Is Your Infrastructure Affected by CVE-2026-48790?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs