OpenTelemetry Python: Unbounded memory allocation in Jaeger baggage propagation

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0038, the 31st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 31 Oct 2026, 14:07 UTC First seen by agentprime
2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-f5m9-jfrj-jjj7
• OSV: GHSA-f5m9-jfrj-jjj7
• github.com/open-telemetry/opentelemetry-python/security/advisories/GHSA-f5m9-jfrj-jjj7
• github.com/open-telemetry/opentelemetry-python/pull/5556
• github.com/open-telemetry/opentelemetry-python/commit/65c4eeb87cd3815dc795d3b5485e9ea0d5affcc7
• github.com/open-telemetry/opentelemetry-python
• github.com/open-telemetry/opentelemetry-python/releases/tag/v1.45.0

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.