cve.bz

CVE-2026-54457 tensorzero tensorzero: SSRF

7.7 highEPSS 0.4%Fix available

High (7.7) in tensorzero tensorzero. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in tensorzero 2026.6.0.

On this page
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.

Severity

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-552 Files or Directories Accessible to External Parties
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • tensorzero (PyPI): fixed in 2026.6.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-54457 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-54457?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-54457?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-54457 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
tensorzero< 2026.6.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-824w-x939-6cmcPyPItensorzero<2026.6.02026.6.0
PYSEC-2026-3541PyPItensorzero<2026.6.02026.6.0

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High
  • CAPEC-150 Collect Data from Common Resource Locations Severity: Medium
  • CAPEC-639 Probe System Files Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON