open-telemetry opentelemetry-ebpf-instrumentation up to 0.8.x Status Message neutralization for logs
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in open-telemetry opentelemetry-ebpf-instrumentation up to 0.8.x. Impacted is an unknown function of the component Status Message Handler. Such manipulation leads to neutralization for logs. This vulnerability is listed as CVE-2026-45679. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability was found in open-telemetry opentelemetry-ebpf-instrumentation up to 0.8.x and classified as critical. Affected by this issue is an unknown code block of the component Status Message Handler. The manipulation with an unknown input leads to a neutralization for logs vulnerability. Using CWE to declare the problem leads to CWE-117. The product does not neutralize or incorrectly neutralizes output that is written to logs. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-45679 since 05/12/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 0.9.0 eliminates this vulnerability. The upgrade is hosted for download at github.com.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.8
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Neutralization for logsCWE: CWE-117 / CWE-116 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: opentelemetry-ebpf-instrumentation 0.9.0
Timeline
05/12/2026 CVE reserved06/02/2026 Advisory disclosed
06/02/2026 VulDB entry created
06/02/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-8rrq-wcg8-cv5q
Status: Confirmed
CVE: CVE-2026-45679 (🔒)
GCVE (CVE): GCVE-0-2026-45679
GCVE (VulDB): GCVE-100-367988
Entry
Created: 06/02/2026 19:30Changes: 06/02/2026 19:30 (65)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.