CVE-2026-45679 OpenTelemetry eBPF Instrumentation: Redis error text is exported in span status messages

Medium 6.5 Published Updated

Attackers can exfiltrate sensitive Redis error data, including tokens and PII, into telemetry backends via OpenTelemetry eBPF instrumentation.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-45679?

CVE-2026-45679 is a medium-severity vulnerability in open-telemetry opentelemetry-ebpf-instrumentation, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-532, CWE-117

Which versions are affected by CVE-2026-45679?

3 open source packages ship an affected version, including go.opentelemetry.io/obi. It affects 1 product.

PackageAffectedFixed in
go.opentelemetry.io/obi GoAll versions0.9.0
go.opentelemetry.io/obi GoAll versions0.9.0
go.opentelemetry.io/obi GoAll versions0.9.0

Products include Opentelemetry Ebpf Instrumentation.

How do I fix CVE-2026-45679?

Upgrade go.opentelemetry.io/obi to 0.9.0 or later.

Is CVE-2026-45679 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45679 exists.

Sources

Also known as GHSA-8rrq-wcg8-cv5q, GO-2026-5265.

Is CVE-2026-45679 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free