CVE-2026-116694: open-telemetry opentelemetry-python · Unthrottled Resource Allocation
Affects open-telemetry opentelemetry-pythonSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.45.0 when convenient.
Data as of 27 Oct 2026, 20:42 UTC
- Patch
- Available – fixed in 1.45.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade open-telemetry opentelemetry-python to 1.45.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| open-telemetryopentelemetry-python | Affected
| Fixed in
|
PyPIopentelemetry-pythonpkg:pypi/opentelemetry-pythonOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade opentelemetry-python to version 1.45.0 or later, where the issue is fixed. No other specific mitigations are indicated. If upgrading is not immediately possible, ensure transport-level limits on input size and number of headers are enforced to reduce exposure.
Description
A resource allocation vulnerability exists in open-telemetry's opentelemetry-python prior to version 1.45.0. The JaegerPropagator.extract() function processes inbound uberctx-* baggage values without limits on entry count or byte size. This can lead to excessive CPU usage and memory allocations when untrusted input contains many or large values, potentially causing denial of service. The issue is fixed in version 1.45.0.
References
- github.com/open-telemetry/opentelemetry-python/security/advisories/GHSA-f5m9-jfrj-jjj7 (opens in a new tab)
- github.com/open-telemetry/opentelemetry-python/pull/5556 (opens in a new tab)
- github.com/open-telemetry/opentelemetry-python/commit/65c4eeb87cd3815dc795d3b5485e9ea0d5affcc7 (opens in a new tab)
- github.com/open-telemetry/opentelemetry-python/releases/tag/v1.45.0 (opens in a new tab)