Vulnerability in go.opentelemetry.io/obi (CVE-2026-45683)
Summary
Vulnerability in go.opentelemetry.io/obi (CVE-2026-45683). Risk of unauthorized operations or information disclosure. Exploitable via bpf_probe_read. Mitigation: upgrade to 0.9.0 or later.
Original description
The description as published by the source.
Summary
The Java TLS ioctl probe reads user-controlled ioctl pointers with bpf_probe_read instead of bpf_probe_read_user. An instrumented local process can therefore point OBI at kernel memory and cause that memory to be copied into telemetry.
Details
The vulnerable path is in bpf/generictracer/java_tls.c. The kprobe hooks do_vfs_ioctl, filters on fd == 0 and the Java TLS magic command, and then treats the third ioctl argument as a structured buffer. It reads fields from that pointer using bpf_probe_read, including:
- the operation byte from
arg - connection metadata from
arg + 1 - the payload length from
arg + 1 + sizeof(connection_info_t)
If len > 0, it computes buf = arg + 1 + sizeof(connection_info_t) + sizeof(u32) and passes that pointer into handle_buf_with_connection.
The next stage, bpf/generictracer/k_tracer_defs.h, uses [bpf_probe_read(args->small_buf, MIN_HTTP2_SIZE, (void *)args->u_buf);](https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/blob/360521…
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-45683 has been found in go.opentelemetry.io/obi.
Attackers can target a specific entry point like bpf_probe_read over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.8/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-45683" on the vendor's site.
CVE-2026-45683 (go.opentelemetry.io/obi) — CWE-127 / CVSS v3 3.8
Attack vector: local / no user interaction
Attack surface: bpf_probe_read / bpf_probe_read_user / do_vfs_ioctl / arg
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-127) exists in go.opentelemetry.io/obi. Attackers reach the vulnerable code path via bpf_probe_read.
Check the vendor advisory for the affected versions of go.opentelemetry.io/obi. Attack surface: bpf_probe_read / bpf_probe_read_user / do_vfs_ioctl / arg.
Severity: Low (CVSS 3.8/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