# CVE-2026-54457: TensorZero: Arbitrary file read and SSRF in TensorZero Gateway's internal object storage endpoint

> Attackers can read arbitrary files or trigger SSRF via the internal object storage endpoint in TensorZero Gateway, potentially exposing credentials or internal services.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-824w-x939-6cmc, PYSEC-2026-3541

## What is CVE-2026-54457?

CVE-2026-54457 is a high-severity server-side request forgery vulnerability in tensorzero, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2026-54457?

3 open source packages ship an affected version, including tensorzero.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tensorzero` | PyPI | All versions | 2026.6.0 |
| `tensorzero` | PyPI | All versions | 2026.6.0 |
| `tensorzero` | PyPI | All versions | 2026.6.0 |

## How do I fix CVE-2026-54457?

Upgrade tensorzero to 2026.6.0 or later.

## Is CVE-2026-54457 being exploited?

There is no known exploitation of CVE-2026-54457 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54457 and fix it if it is affected.

What it is: CVE-2026-54457 is a high-severity server-side request forgery vulnerability in tensorzero, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54457 in the wild and no public exploit code.

Affected packages and fixed versions:
- tensorzero (PyPI): affected all versions; fixed in 2026.6.0
- tensorzero (PyPI): affected all versions; fixed in 2026.6.0
- tensorzero (PyPI): affected all versions; fixed in 2026.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54457/ (Markdown: https://insights.sbomify.com/CVE-2026-54457/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54457
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54457
- OSV: https://osv.dev/vulnerability/CVE-2026-54457

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54457/
Summaries are generated and may contain mistakes; the official description above is the record.