CVE-2026-45685 json
OpenTelemetry eBPF Instrumentation: MongoDB parser panics on malformed wire messages
published 5mo ago modified 3mo ago also EUVD-2026-33958 , GHSA-j8p6-96vp-f3r9 , GO-2026-5456
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. From version 0.1.0 to before version 0.9.0, malformed MongoDB wire messages can trigger uncaught panics in the MongoDB TCP parser, allowing a remote unauthenticated attacker to crash the telemetry agent and cause a denial of service. The parser operates on raw attacker-controlled network payloads before the input is fully validated, so a single crafted message can terminate telemetry collection for the affected process or node. This issue has been patched in version 0.9.0.
Patch / fix
- go go.opentelemetry.io/obi 0.9.0
- opentelemetry ebpf_instrumentation 0.9.0
- opentelemetry opentelemetry_ebpf_instrumentation 0.9.0
- alloy SLE Module for Basesystem 15 SP7 1.17.1-150700.15.23.1
- alloy SLES for SAP applications 16.0, SLES 16.0 1.17.0-160000.1.1
suse advisories SUSE-SU-2026:2824-1SUSE-SU-2026:22575-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
- alloy openSUSE Leap 16.0 1.17.0-160000.1.1
- alloy openSUSE Tumbleweed 1.17.0-1.1
opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2026:21251-1openSUSE-SU-2026:11053-1
Is CVE-2026-45685 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 5mo ago
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/security/advisories/GHSA-j8p6-96vp-f3r9 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | go.opentelemetry.io/obi | <0.9.0 |
0.9.0 |
Affected products
- open-telemetry opentelemetry-ebpf-instrumentation
Classification
References
-
github.com
/open-telemetry/opentelemetry-ebpf-instrumentation/security/advisories/GHSA-j8p6-96vp-f3r9
exploit, web, vendor-advisory, advisory
-
github.com
/open-telemetry/opentelemetry-ebpf-instrumentation/releases/tag/v0.9.0
web, product, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-45685
advisory
-
github.com
/open-telemetry/opentelemetry-ebpf-instrumentation
package
Sources
- CVE List CVE-2026-45685
- GitHub Advisory GHSA-j8p6-96vp-f3r9
- NVD CVE-2026-45685
- OSV GO-2026-5456
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.