# CVE-2026-112006: OpenTelemetry opentelemetry-exporter-otlp-proto-http 1.5.0 before 1.45.0 Improper Certificate Validation

> Man-in-the-middle attackers can intercept or modify telemetry data by exploiting disabled TLS verification when certificate environment variables are empty.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-112006, GHSA-6469-8p9h-mmvm, UBUNTU-CVE-2026-112006

## What is CVE-2026-112006?

CVE-2026-112006 is a high-severity vulnerability in opentelemetry-exporter-otlp-proto-http, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenTelemetry opentelemetry-exporter-otlp-proto-http 1.5.0 before 1.45.0 contains an improper certificate validation vulnerability that disables TLS verification when OTEL_EXPORTER_OTLP_CERTIFICATE variables are empty strings. Man-in-the-middle attackers can impersonate the collector to read or alter exported traces, metrics, and logs, including authentication headers from OTEL_EXPORTER_OTLP_HEADERS.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-112006?


## How do I fix CVE-2026-112006?

Upgrade to a fixed version.

## Is CVE-2026-112006 being exploited?

There is no known exploitation of CVE-2026-112006 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112006 and fix it if it is affected.

What it is: CVE-2026-112006 is a high-severity vulnerability in opentelemetry-exporter-otlp-proto-http, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-112006 in the wild and no public exploit code.

Affected product: opentelemetry-exporter-otlp-proto-http. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112006/ (Markdown: https://insights.sbomify.com/CVE-2026-112006/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112006
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112006
- OSV: https://osv.dev/vulnerability/CVE-2026-112006

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112006/
Summaries are generated and may contain mistakes; the official description above is the record.