Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/open-telemetry/opentelemetry-python/commit/65c4eeb87cd3815dc7
- https://github.com/open-telemetry/opentelemetry-python/pull/5556
- https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.45.0
- https://github.com/open-telemetry/opentelemetry-python/security/advisories/GHSA-
FAQ
What is CVE-2026-116694?
CVE-2026-116694 is a documented vulnerability. 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 withou...
How severe is CVE-2026-116694?
CVSS scoring is not yet available for CVE-2026-116694. Check NVD for updates.
Is there a patch for CVE-2026-116694?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.