Skip to main content
← All vulnerabilities
CVE-2026-116694GHSA-F5M9-JFRJ-JJJ7EUVD-2026-111385

OpenTelemetry Python: Unbounded memory allocation in Jaeger baggage propagation

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 1.45.0
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

OpenTelemetry Python's Jaeger propagator (opentelemetry-propagator-jaeger) is affected when enabled, because it accepts incoming baggage values without size or count limits. An attacker who can send crafted requests with many or very large baggage values could force excessive CPU and memory use, potentially causing a denial of service in services that do not restrict input size at the transport level.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.0, JaegerPropagator.extract() in opentelemetry-propagator-jaeger processes inbound uberctx-* baggage values without entry, per-entry byte, or total-byte limits. Services that enable the optional Jaeger propagator can perform unnecessary CPU work and short-lived heap allocations when an untrusted carrier supplies numerous or oversized values, contributing to denial of service when transport-level limits do not constrain the input. Common default Python HTTP server limits reduce the practical impact, while custom getters, non-HTTP transports, or raised header limits increase exposure. This issue is fixed in version 1.45.0.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • open-telemetry opentelemetry-python

    fixed in 1.45.0

  • opentelemetry-propagator-jaegerPyPI

    fixed in 1.45.0

References 4

GitHub · open-telemetry/opentelemetry-python