Sign in Sign up
JA · EN · FR
SecPulse
← Back
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.

AI summary snake-internal / snake-material-v2

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`` without authentication.
📍 Affected scope
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 (7 steps)

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. 5
    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. 6
    Apply patch patch 
    Upgrade tensorzero to 2026.6.0

    ステージング環境で 2026.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

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

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →