CVE Intelligence
Medium Denial of service

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

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.

Published Oct 27, 2026 · Updated Oct 27, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Open-telemetry
Opentelemetry-python and 1 more
CVSS base
6.3
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Pip Opentelemetry-propagator-jaeger: fixed in version 1.45.0 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Open-telemetry Opentelemetry-python, Pip Opentelemetry-propagator-jaeger).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Open-telemetry Opentelemetry-python version < 1.45.0 Vulnerable CVE Program (cve.org) e CISA ADP
Pip Opentelemetry-propagator-jaeger ≤ 1.44.0 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Attack requirements
Present
Privileges required
None
User interaction
None
Scope
X
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
None
Availability (vulnerable system)
Low
Confidentiality (subsequent)
None
Integrity (subsequent)
None
Availability (subsequent)
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.3 CVSS 4.0 Medium — — security-advisories@github.com via NIST National Vulnerability Database
6.3 CVSS 4.0 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-770 · Allocation of Resources Without Limits or Throttling

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Track CPU/memory spikes and availability drops correlated with request patterns.
web/proxy/WAF logsnetwork IDS/IPSresource metrics

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 27, 2026 · GitHub Security Advisories
  • Affected products added · pip/opentelemetry-propagator-jaeger
    Oct 27, 2026 · GitHub Security Advisories
  • Affected products added · open-telemetry/opentelemetry-python
    Oct 27, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 27, 2026
  • CVSS changed · 6.3
    Oct 27, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 27, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 27, 2026 · Alertas do Telegram
  • CVE published
    Oct 27, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 27, 2026 – Oct 27, 2026
  • 1× Official description updated · Oct 27, 2026 – Oct 27, 2026

References

5 on the record

Elsewhere on this site

Open-telemetry
every CVE for this vendor
CWE-770
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-114603 OpenTelemetry Python: Unbounded tracestate parsing in opentelemetry-api 5d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-116694 is "OpenTelemetry Python: Unbounded memory allocation in Jaeger baggage propagation", rated Medium. It affects Opentelemetry-python (Open-telemetry); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.