Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-45679: CWE-117: Improper Output Neutralization for Logs in open-telemetry opentelemetry-ebpf-instrumentation

0
Medium
VulnerabilityCVE-2026-45679cvecve-2026-45679cwe-117cwe-532
Published: Tue Jun 02 2026 (06/02/2026, 15:24:31 UTC)
Source: CVE Database V5
Vendor/Project: open-telemetry
Product: opentelemetry-ebpf-instrumentation

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.

CVSS v3.1

Score 6.5medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 06/02/2026, 16:04:56 UTC

Technical Analysis

CVE-2026-45679 describes an improper output neutralization vulnerability (CWE-117) in open-telemetry's opentelemetry-ebpf-instrumentation prior to version 0.9.0. The product exports raw Redis error text as span status messages, which may contain sensitive or attacker-controlled data. This can result in exfiltration of confidential information into telemetry backends and injection of untrusted text into downstream systems. The vulnerability has been patched in version 0.9.0.

Potential Impact

The vulnerability allows sensitive or attacker-controlled data from Redis error replies to be logged and transmitted in telemetry spans without sanitization. This can lead to unintended exposure of tokens, personally identifiable information, or other confidential inputs to telemetry backends and analysis tools. There is no indication of impact on system availability or integrity. No known exploits in the wild have been reported.

Mitigation Recommendations

Upgrade opentelemetry-ebpf-instrumentation to version 0.9.0 or later, where this issue has been fixed. Patch status is confirmed by the vendor advisory indicating the fix in version 0.9.0. No additional mitigation steps are specified.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-05-12T21:59:25.667Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a1efb6ae29bf47b50db3b30

Added to database: 6/2/2026, 3:48:58 PM

Last enriched: 6/2/2026, 4:04:56 PM

Last updated: 6/3/2026, 5:03:14 AM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses