OpenTelemetry Python: Unbounded tracestate parsing in opentelemetry-api

Why it is Yellow

• CVSS 5.3 medium
• Public exploit or proof of concept referenced
• On your watchlist: python, PyPI

Affected packages

References

• https://github.com/advisories/GHSA-xcq7-p3pf-p88h
• https://github.com/open-telemetry/opentelemetry-python/security/advisories/GHSA-xcq7-p3pf-p88h
• https://github.com/open-telemetry/opentelemetry-python/pull/5749
• https://github.com/open-telemetry/opentelemetry-python/commit/d5224bf4ffdf2aee1b592ad238dcc32ca957f26b
• https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md#version-1451066b1-2026-10-06
• https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.45.1
• https://github.com/advisories/GHSA-xcq7-p3pf-p88h

Original 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.