Vulnerability in go.opentelemetry.io/obi (CVE-2026-45679)
Summary
Vulnerability in go.opentelemetry.io/obi (CVE-2026-45679). Risk of unauthorized operations or information disclosure. Exploitable via getRedisError. Mitigation: upgrade to 0.9.0 or later.
Original description
The description as published by the source.
Summary
OBI exports raw Redis error text as the span status message. Because Redis error replies can contain attacker-controlled or sensitive values, this behavior can exfiltrate tokens, PII, or other confidential input into telemetry backends and inject untrusted text into downstream analysis systems.
Details
In pkg/ebpf/common/redis_detect_transform.go, getRedisError trims the raw error buffer and stores it directly in request.DBError.Description.
Later, pkg/appolly/app/request/span.go returns that description as the exported status message for Redis spans whenever the span status is non-zero.
There is no opt-in control or sanitization beyond CRLF trimming. As a result, raw Redis error text becomes part of OTLP-exported status metadata by default.
PoC
Local request-layer testing recorded a status message containing ERR invalid password for user bob secret=TOPSECRET, which shows that unfiltered Redis error text reaches the exported status message.
Use a vulnerable build:
git checkout v0.0.0-rc.1+build
make build
Start Redis and OBI:
docker run --rm -p 6379:6379 redis:7
sudo ./bin/obi
Send a comman…
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-45679 has been found in go.opentelemetry.io/obi.
Attackers can target a specific entry point like getRedisError over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/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-45679" on the vendor's site.
CVE-2026-45679 (go.opentelemetry.io/obi) — CWE-117 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: getRedisError / request.DBError.Description
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-117) exists in go.opentelemetry.io/obi. Attackers reach the vulnerable code path via getRedisError without authentication.
Check the vendor advisory for the affected versions of go.opentelemetry.io/obi. Attack surface: getRedisError / request.DBError.Description.
Severity: Medium (CVSS 6.5/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 nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com