Vulnerability in tensorzero (CVE-2026-54457)
Summary
Vulnerability in tensorzero (CVE-2026-54457). Confidential information can be exposed externally. Exploitable via storage_path. Mitigation: upgrade to 2026.6.0 or later.
Original description
The description as published by the source.
Impact
The /internal/object_storage endpoint accepts a caller-supplied JSON storage_path parameter that dynamically overrides the TensorZero [object_storage] configuration.
By abusing the filesystem storage type, a caller can read arbitrary files from the gateway filesystem, including files that may contain sensitive credentials. Similarly, by abusing the s3_compatible storage type, the caller can coerce the gateway into making outbound object storage requests to attacker-chosen internal/cloud-metadata endpoints.
This vulnerability only applies when the gateway can be accessed by untrusted callers. If a developer's TensorZero deployment has authentication enabled, only authenticated callers can exploit this vulnerability. If a developer's deployment has authentication disabled, any caller can exploit this vulnerability.
Remediation
The vulnerability has been patched in version 2026.6.0. See PR #7527.
Workarounds
If developers are unable to upgrade a gateway that is exposed to untrusted callers, please block external access to the /internal/object_storage endpoint.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54457 has been found in tensorzero.
Attackers can target a specific entry point like storage_path over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade tensorzero to 2026.6.0 or later.
If unsure, ask your IT team or search "tensorzero CVE-2026-54457" on the vendor's site.
CVE-2026-54457 (tensorzero) — CWE-552 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: storage_path / filesystem / s3_compatible
Patched: 2026.6.0 — apply immediately
Workaround: If developers are unable to upgrade a gateway that is exposed to untrusted callers, please block external access to the /internal/object_storage endpoint.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-552) exists in tensorzero. Attackers reach the vulnerable code path via storage_path.
Check the vendor advisory for the affected versions of tensorzero. Attack surface: storage_path / filesystem / s3_compatible.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 2026.6.0.
Workaround: If developers are unable to upgrade a gateway that is exposed to untrusted callers, please block external access to the /internal/object_storage endpoint.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tensorzero' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tensorzero' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tensorzeroを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If developers are unable to upgrade a gateway that is exposed to untrusted callers, please block external access to the `/internal/object_storage` endpoint.パッチが適用されるまでの応急処置として、If developers are unable to upgrade a gateway that is exposed to untrusted callers, please block external access to the
/internal/object_storageendpoint. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade tensorzero to 2026.6.0ステージング環境で 2026.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com