Quick answers
- Is CVE-2026-112006 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112006 being exploited in the wild.
- How severe is CVE-2026-112006?
- Medium severity, with a CVSS score of 6.5, published 18 October 2026.
- Which products and versions are affected?
- Opentelemetry-Exporter-Otlp-Proto-Http 1.5.0 before 1.45.0.
- Is there a fix for CVE-2026-112006?
- Yes: fixed in 1.45.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112006 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-112006?
- Check whether you run Opentelemetry-Exporter-Otlp-Proto-Http 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
- Fixed in: 1.45.0
Technical details
The exporter improperly validates certificate configuration: when OTEL_EXPORTER_OTLP_CERTIFICATE environment variables are set to empty strings, TLS verification is disabled instead of being enforced with defaults. An attacker on the network can perform man-in-the-middle attacks to read or modify exported traces, metrics, logs, and headers without the application detecting the compromise. The fix is available in version 1.45.0.
Affected products
- OpenTelemetry opentelemetry-exporter-otlp-proto-http 1.5.0 before 1.45.0
Timeline
- 2026-10-18: disclosed