Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54457 high CVSS 7.7

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.

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.

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.

❓ What is the problem

A vulnerability (CWE-552) exists in tensorzero. Attackers reach the vulnerable code path via storage_path.

📍 Affected scope

Check the vendor advisory for the affected versions of tensorzero. Attack surface: storage_path / filesystem / s3_compatible.

🔥 Severity

Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2026.6.0.

🛡️ Workaround

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.

🔍 Detection

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

  1. 1
    Identify exposure identify 
    grep -r 'tensorzero' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で tensorzero を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply 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_storage endpoint. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade tensorzero to 2026.6.0

    ステージング環境で 2026.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip tensorzero
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.6.0"}]}]
PyPI tensorzero
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.6.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details