Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.new Create a CVE report
Check your stack
CVE-2026-114603medium5.3

OpenTelemetry Python: Unbounded tracestate parsing in opentelemetry-api

Impact

OpenTelemetry Python versions prior to 1.45.1 have an unbounded tracestate parsing vulnerability, allowing unauthenticated requests with malformed headers to cause excessive CPU time usage, impacting availability. The issue is due to an inefficient regular expression in the opentelemetry-api function. The impact is limited to availability.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

open-telemetry · GitHub_M

opentelemetry-python

1 range
GitHub_M version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

< 1.45.1

unaffected

unknown

Other versions: unknown

Original source description

OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.1, the opentelemetry-api function TraceState.from_header in opentelemetry/trace/span.py, reached through TraceContextTextMapPropagator.extract, parses inbound W3C tracestate headers with an unbounded optional-whitespace regular expression. A malformed header containing a long run of spaces or tabs without a following comma causes quadratic backtracking before the member-count limit is applied. Services using the default W3C Trace Context propagator can therefore spend excessive CPU time on one unauthenticated request when the HTTP server, parser, gateway, or custom carrier accepts a sufficiently large header. The processing can occupy a synchronous worker or delay unrelated requests on the same asynchronous event loop. The impact is limited to availability and does not expose or modify telemetry data or allow code execution. This issue is fixed in version 1.45.1.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-114603

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-400 ↗

CWE-400: Uncontrolled Resource Consumption

GitHub_M

Related →
CWE-1333 ↗

CWE-1333: Inefficient Regular Expression Complexity

GitHub_M

Related →
Contributing organizations · 2
GitHub_M

Assigning organization

2026-10-22
CISA-ADP

Additional data publisher

2026-10-29

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

5 sources
github.com/open-telemetry/opentelemetry-python/security/advisories/GHSA-xcq7-p3pf-p88h
exploitGitHub_M · CISA-ADP
github.com/open-telemetry/opentelemetry-python/pull/5749
PatchGitHub_M
github.com/open-telemetry/opentelemetry-python/commit/d5224bf4ffdf2aee1b592ad238dcc32ca957f26b
PatchGitHub_M
github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md
Release notesGitHub_M
github.com/open-telemetry/opentelemetry-python/releases/tag/v1.45.1
Release notesGitHub_M