Skip to content
Fencer Intel
medium 6.5

CVE-2026-45679 json

OpenTelemetry eBPF Instrumentation: Redis error text is exported in span status messages

published 5mo ago modified 3mo ago also EUVD-2026-33953 , GHSA-8rrq-wcg8-cv5q , GO-2026-5265

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 11%
public exploits
0
none known

Summary

OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. Prior to version 0.9.0, 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. 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 SLES for SAP applications 16.0, SLES 16.0 1.19.2-160000.1.1
  • alloy SLE Module for Basesystem 15 SP7 1.19.2-150700.15.29.1

suse advisories SUSE-SU-2026:24148-1SUSE-SU-2026:4408-1

  • alloy openSUSE Leap 16.0 1.19.2-160000.1.1
  • alloy openSUSE Tumbleweed 1.19.2-1.1
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:22032-1openSUSE-SU-2026:11803-1openSUSE-SU-2026:21483-1

Is CVE-2026-45679 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 Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 11% 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-8rrq-wcg8-cv5q referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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

Weakness
  • CWE-117 Improper Output Neutralization for Logs
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

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.