Is CVE-2026-45679 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-45679 being exploited in the wild.

How severe is CVE-2026-45679?

Medium severity, with a CVSS score of 6.5, published 2 June 2026.

Which products and versions are affected?

go.opentelemetry.io/obi (Go) < 0.9.0, SEMVER:introduced=0,fixed=0.9.0; Opentelemetry Ebpf Instrumentation Prior to 0.9.0.

Is there a fix for CVE-2026-45679?

Yes. go.opentelemetry.io/obi (Go): upgrade to 0.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-45679 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-45679?

Check whether you run go.opentelemetry.io/obi (Go), Opentelemetry Ebpf Instrumentation or Opentelemetry Otelhttp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-45679: OpenTelemetry eBPF Instrumentation information disclosure in Redis spans

Q: Is there a fix for CVE-2026-45679?

Yes. go.opentelemetry.io/obi (Go): upgrade to 0.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-45679 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-45679?

Check whether you run go.opentelemetry.io/obi (Go), Opentelemetry Ebpf Instrumentation or Opentelemetry Otelhttp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-45679 · Severity: medium · CVSS 6.5 · Published 2026-06-02

OpenTelemetry eBPF Instrumentation is a tool used to monitor application performance by capturing network traffic data. A security issue was identified where the tool automatically captures and exports raw error messages from Redis databases into monitoring dashboards and logs. Because these error messages can contain sensitive information like passwords, tokens, or personal data, an attacker could potentially trick the system into leaking confidential information into telemetry systems or inject misleading data into analysis tools.

Technologies: go.opentelemetry.io/obi (Go), Opentelemetry Ebpf Instrumentation, Opentelemetry Otelhttp. Vendors: Go, Opentelemetry.

Quick answers

Is CVE-2026-45679 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-45679 being exploited in the wild.
How severe is CVE-2026-45679?: Medium severity, with a CVSS score of 6.5, published 2 June 2026.
Which products and versions are affected?: go.opentelemetry.io/obi (Go) < 0.9.0, SEMVER:introduced=0,fixed=0.9.0; Opentelemetry Ebpf Instrumentation Prior to 0.9.0.
Is there a fix for CVE-2026-45679?: Yes. go.opentelemetry.io/obi (Go): upgrade to 0.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-45679 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-45679?: Check whether you run go.opentelemetry.io/obi (Go), Opentelemetry Ebpf Instrumentation or Opentelemetry Otelhttp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

go.opentelemetry.io/obi (Go): upgrade to 0.9.0 or later
```
go get go.opentelemetry.io/obi@v0.9.0
```

Technical details

The vulnerability exists in the Redis instrumentation logic within OpenTelemetry eBPF Instrumentation (OBI). Specifically, in `pkg/ebpf/common/redis_detect_transform.go`, the `getRedisError` function trims raw error buffers and stores them directly in `request.DBError.Description` without sanitization. This description is subsequently exported as the status message for Redis spans in `pkg/appolly/app/request/span.go`. An attacker can trigger Redis errors containing sensitive or controlled strings (e.g., via malformed commands), which are then automatically exfiltrated to OTLP-exported telemetry backends. This issue is classified under CWE-117 (Improper Output Neutralization for Logs) and CWE-532 (Insertion of Sensitive Information into Log File). The issue is patched in version 0.9.0, which makes database error reporting optional and disabled by default.

Affected products

OpenTelemetry OpenTelemetry eBPF Instrumentation (OBI) / go.opentelemetry.io/obi Prior to 0.9.0

Identifiers

CVE-2026-45679
GHSA-8rrq-wcg8-cv5q
GO-2026-5265

Timeline

2026-05-11: patched: Version 0.9.0 released
2026-05-12: advisory: GitHub Security Advisory published
2026-06-02: disclosed: CVE-2026-45679 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.