CVE-2026-54457

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd 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
7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

TensorZero is an open-source LLMOps platform that unifies an LLM gateway, observability, evaluation, optimization, and experimentation. Prior to 2026.6.0, the TensorZero Gateway /internal/object_storage endpoint accepts a caller-supplied JSON storage_path parameter that dynamically overrides the [object_storage] configuration. Selecting the filesystem storage type allows arbitrary files on the gateway filesystem to be read, including credential files. Selecting the s3_compatible storage type causes outbound object-storage requests to attacker-chosen internal or cloud-metadata endpoints. Exploitation requires access to the gateway, which can be authenticated or unauthenticated depending on deployment configuration. This issue is fixed in version 2026.6.0.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity77% × 45%
The EG Score, 7.7 of 10.
Exploitation0.4% × 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.4%
EPSS %ILE
32nd
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

July 15, 2026

Last Modified

September 11, 2026

Advisory Details (3)

Auto-updated Aug 21, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

2026.6.0

Patch available: tensorzero/tensorzero 2026.6.0

https://github.com/tensorzero/tensorzero/releases/tag/2026.6.0
GitHub commit Patch Available

commit 0abbc838bae3 (tensorzero/tensorzero)

Patch available: tensorzero/tensorzero 2026.6.0 (contains commit 0abbc838bae3)

https://github.com/tensorzero/tensorzero/commit/0abbc838bae3394fe7491dad7009670d4e3b6cf8
GitHub advisoryMentions a patch (unverified)

Arbitrary file read and SSRF in TensorZero Gateway's internal object storage endpoint · Advisory · tensorzero/tensorzero · GitHub

https://github.com/tensorzero/tensorzero/security/advisories/GHSA-824w-x939-6cmc

Vendor Advisories for CVE-2026-54457(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)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
tensorzero2025.10.0 ... 2026.5.2 (64 versions)
  • every version up to 2026.6.0: fixed in 2026.6.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 34× 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-13 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-12 15:56 UTCEG score recompute
  4. 2026-10-11 19:39 UTCEG score recompute
  5. 2026-10-11 16:54 UTCEG score recompute
  6. 2026-10-11 14:18 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-01 12:35 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-09-28 08:40 UTCEG score recompute
  22. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-09-24 08:45 UTCEG score recompute
Show 44 more
  1. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-09-23 03:14 UTCEG score recompute
  3. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  5. 2026-09-18 04:42 UTCEG score recompute
  6. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-09-13 23:11 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-09-13 07:11 UTCEG score recompute
  13. 2026-09-11 18:36 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-09-08 00:40 UTCEG score recompute
  18. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-09-05 20:45 UTCEG score recompute
  21. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-08-31 05:45 UTCEG score recompute
  26. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  27. 2026-08-30 03:43 UTCEG score recompute
  28. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  29. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  30. 2026-08-28 01:51 UTCEG score recompute
  31. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-08-26 22:57 UTCEG score recompute
  33. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  34. 2026-08-25 14:21 UTCEG score recompute
  35. 2026-08-25 14:00 UTCEG score recompute
  36. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  37. 2026-08-24 14:31 UTCEG score recompute
  38. 2026-08-23 12:27 UTCEG score recompute
  39. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  40. 2026-08-21 21:25 UTCEG score recompute
  41. 2026-07-30 21:41 UTCEG score recompute
  42. 2026-07-26 11:28 UTCEG score recompute
  43. 2026-07-23 03:19 UTCEG score recompute
  44. 2026-07-15 22:19 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54457?
CVE-2026-54457 is a high-severity vulnerability; its CVE record was published on July 15, 2026. TensorZero is an open-source LLMOps platform that unifies an LLM gateway, observability, evaluation, optimization, and experimentation. Prior to 2026.6.0, the TensorZero Gateway /internal/objectstorage endpoint accepts a caller-supplied JSON storagepath parameter that dynamically overrides the…
When was the CVE record for CVE-2026-54457 published?
The CVE record for CVE-2026-54457 was published on July 15, 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 11, 2026; the record at its source may have been updated since.
Is CVE-2026-54457 actively exploited?
CVE-2026-54457 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54457?
CVE-2026-54457 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54457?
A fix for CVE-2026-54457 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54457 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-54457

Explore →

Is Your Infrastructure Affected by CVE-2026-54457?

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

Book a Demo →Browse All CVEs