NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2026-116694: OpenTelemetry Python: Unbounded memory allocation in Jaeger baggage propagation

mediumCVSS 4.0 6.3GHSA-f5m9-jfrj-jjj7

opentelemetry-propagator-jaeger before 1.45.0 does not limit how much baggage JaegerPropagator.extract() reads from inbound uberctx-* headers. An unauthenticated remote sender can make a service burn extra CPU and memory per request. Only services that install and enable the Jaeger propagator are affected. Upgrade to 1.45.0.

Published Oct 27, 2026 · Analysis Nov 1, 2026

What an attacker can do

JaegerPropagator.extract() reads every inbound header that starts with the uberctx- prefix and turns each into a baggage entry. Before 1.45.0 it applied no cap on the number of entries or their size. A sender who can put many or very large uberctx-* headers on a request makes the service decode all of them, which costs CPU and short-lived heap allocations.

The damage is limited to availability. The advisory says the flaw does not expose or change telemetry data and does not give code execution. The CVSS 4.0 vector rates only low availability impact.

In practice the risk is small for most Python web services. The package is a separate install, and the default OpenTelemetry Python configuration does not enable the Jaeger propagator. Gunicorn defaults (100 header fields, 8,190 bytes each) and Uvicorn's h11 buffer (16,384 bytes) already bound what reaches the propagator. The risk is higher for non-HTTP transports, custom TextMapGetter implementations, and deployments where proxy or server header limits were raised or removed.

Who is affected

All releases of opentelemetry-propagator-jaeger up to and including 1.44.0 are affected. You are exposed only if the package is installed and the Jaeger propagator is enabled (for example through OTEL_PROPAGATORS including jaeger), and untrusted callers can reach the service. Check the installed version:

pip show opentelemetry-propagator-jaeger

Check whether the propagator is enabled with echo $OTEL_PROPAGATORS or by searching your code for JaegerPropagator.

opentelemetry-propagator-jaeger

Ecosystem
PyPI
Affected
<= 1.44.0
Fixed in
1.45.0
Check
pip show opentelemetry-propagator-jaeger

How to fix it

Upgrade opentelemetry-propagator-jaeger to 1.45.0 or later:

pip install --upgrade "opentelemetry-propagator-jaeger>=1.45.0"

Version 1.45.0 reads at most 180 entries and 8,192 total bytes, and skips any entry larger than 4,096 bytes. These are the W3C Baggage limits. Further members are dropped once a limit is reached. The advisory names no workaround. Keeping request-header limits at the server or gateway low also reduces the exposure.

How to tell if you were hit

The flaw leaves no dedicated log line. Look for requests with an unusually large number of uberctx-* headers, or very large ones, in gateway and access logs. Correlate them with CPU spikes or memory churn in the instrumented service. Also check non-HTTP transports and custom TextMapGetter code, where server header limits do not apply.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Summary

JaegerPropagator.extract() in opentelemetry-propagator-jaeger did not enforce limits when extracting inbound uberctx-* baggage headers. Attacker-controlled baggage could cause unnecessary CPU work and short-lived heap allocations while processing more data than the propagator should accept.

Impact

Services that enable the optional Jaeger propagator and accept untrusted inbound propagation headers may experience increased per-request resource usage. This can contribute to denial-of-service risk when transport-level limits are absent or configured above the baggage limits.

The practical impact for most Python web deployments is limited. The package must be installed separately, and the Jaeger propagator is not enabled by the default OpenTelemetry Python configuration.

Common Python web servers also constrain request headers before they reach the propagator:

  • Gunicorn allows a maximum of 100 request-header fields and 8,190 bytes per field by default.
  • Uvicorn’s h11 implementation limits its incomplete-event buffer to 16,384 bytes by default.

The risk is higher for non-HTTP transports, custom TextMapGetter implementations, or deployments where server and gateway limits have been increased or disabled.

The impact is limited to availability. This issue does not expose or modify telemetry data and does not allow code execution.

Patches

Versions of opentelemetry-propagator-jaeger earlier than 1.45.0 are affected.

Upgrade opentelemetry-propagator-jaeger to version 1.45.0 or later.

Version 1.45.0 limits extraction to 180 entries and 8,192 total bytes and skips entries larger than 4,096 bytes.

Credit

tonghuaroot

Credited to tonghuaroot.

Questions

Is the Jaeger propagator on by default in OpenTelemetry Python?

No. The package must be installed separately and enabled. The default OpenTelemetry Python configuration does not use it, so most deployments are not exposed.

Can this flaw lead to code execution or data leaks?

No. The advisory states the impact is limited to availability. It does not expose or modify telemetry data and does not allow code execution.

What limits does opentelemetry-propagator-jaeger 1.45.0 enforce?

Extraction stops at 180 entries and 8,192 total bytes, and entries larger than 4,096 bytes are skipped. The pull request also applies the same cap to inject.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology