Vulnerability in go.opentelemetry.io/obi (CVE-2026-45684)
Summary
Vulnerability in go.opentelemetry.io/obi (CVE-2026-45684). Risk of unauthorized operations or information disclosure. Exploitable via writev. Mitigation: upgrade to 0.9.0 or later.
Original description
The description as published by the source.
OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. From version 0.7.0 to before version 0.9.0, OBI's log enricher mishandles writev buffers by reading only the first iovec entry but using the total iov_iter.count as the copy length. When log injection is enabled, a crafted multi-segment writev call can make OBI read and overwrite memory beyond the first segment. This issue has been patched in version 0.9.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-45684 has been found in go.opentelemetry.io/obi.
Attackers can target a specific entry point like writev over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.9/10.
What to do: upgrade go.opentelemetry.io/obi to 0.9.0 or later.
If unsure, ask your IT team or search "go.opentelemetry.io/obi CVE-2026-45684" on the vendor's site.
CVE-2026-45684 (go.opentelemetry.io/obi) — CWE-126 / CVSS v3 4.9
Attack vector: local / unauthenticated / no user interaction
Attack surface: writev / iovec / iov_iter.count / __fill_iov
Patched: 0.9.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.
A vulnerability (CWE-126) exists in go.opentelemetry.io/obi. Attackers reach the vulnerable code path via writev without authentication.
Check the vendor advisory for the affected versions of go.opentelemetry.io/obi. Attack surface: writev / iovec / iov_iter.count / __fill_iov.
Severity: Medium (CVSS 4.9/10). Risk of unauthorized operations or information disclosure.
Update to 0.9.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade go.opentelemetry.io/obi to 0.9.0ステージング環境で 0.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com