← Back
CVE-2026-41433 high CVSS 8.4

Path Traversal in go.opentelemetry.io/obi (CVE-2026-41433)

Summary

path traversal in go.opentelemetry.io/obi (CVE-2026-41433). Data can be tampered with by attackers. Exploitable via ``TMPDIR``. Mitigation: upgrade to `0.8.0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-41433** has been found in go.opentelemetry.io/obi. Attackers can target a specific entry point like ``TMPDIR`` over the network to misuse the product. Data can be tampered with by attackers. CVSS score: 8.4/10. What to do: upgrade go.opentelemetry.io/obi to **0.8.0** or later. If unsure, ask your IT team or search "go.opentelemetry.io/obi CVE-2026-41433" on the vendor's site.
CVE-2026-41433 (go.opentelemetry.io/obi) — CWE-22 / CVSS v3 8.4 Attack vector: local / no user interaction Attack surface: `TMPDIR` / `root` / `dir` / `filepath.Join` Patched: `0.8.0` — apply immediately 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
**Path traversal** (CWE-22) exists in go.opentelemetry.io/obi. Attackers reach the vulnerable code path via ``TMPDIR`` without authentication.
📍 Affected scope
go.opentelemetry.io/obi — . Attack surface: `TMPDIR` / `root` / `dir` / `filepath.Join`.
🔥 Severity
Severity: High (CVSS 8.4/10). Data can be tampered with by attackers
🔧 How to fix
Update to **0.8.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'go.opentelemetry.io/obi' .` 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 'go.opentelemetry.io/obi' . | grep -v node_modules

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

  2. 6
    Apply patch patch
    Upgrade go.opentelemetry.io/obi to 0.8.0

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

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

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

Affected packages

Go go.opentelemetry.io/obi
[{"type":"SEMVER","events":[{"introduced":"0.4.0"},{"fixed":"0.8.0"}]}]

References

🍪 About cookies

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

Details →