GHSA-F5M9-JFRJ-JJJ7
Vulnerability from github – Published: 2026-10-27 21:06 – Updated: 2026-10-27 21:06Summary
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
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.44.0"
},
"package": {
"ecosystem": "PyPI",
"name": "opentelemetry-propagator-jaeger"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.45.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-116694"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-27T21:06:54Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "## Summary\n\n`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.\n\n## Impact\n\nServices 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.\n\nThe 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.\n\nCommon Python web servers also constrain request headers before they reach the propagator:\n\n- Gunicorn allows a maximum of 100 request-header fields and 8,190 bytes per field by default.\n- Uvicorn\u2019s h11 implementation limits its incomplete-event buffer to 16,384 bytes by default.\n\nThe risk is higher for non-HTTP transports, custom `TextMapGetter` implementations, or deployments where server and gateway limits have been increased or disabled.\n\nThe impact is limited to availability. This issue does not expose or modify telemetry data and does not allow code execution.\n\n## Patches\n\nVersions of `opentelemetry-propagator-jaeger` earlier than `1.45.0` are affected.\n\nUpgrade `opentelemetry-propagator-jaeger` to version `1.45.0` or later.\n\nVersion `1.45.0` limits extraction to 180 entries and 8,192 total bytes and skips entries larger than 4,096 bytes.\n\n## Credit\n\ntonghuaroot",
"id": "GHSA-f5m9-jfrj-jjj7",
"modified": "2026-10-27T21:06:54Z",
"published": "2026-10-27T21:06:54Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/open-telemetry/opentelemetry-python/security/advisories/GHSA-f5m9-jfrj-jjj7"
},
{
"type": "WEB",
"url": "https://github.com/open-telemetry/opentelemetry-python/pull/5556"
},
{
"type": "WEB",
"url": "https://github.com/open-telemetry/opentelemetry-python/commit/65c4eeb87cd3815dc795d3b5485e9ea0d5affcc7"
},
{
"type": "PACKAGE",
"url": "https://github.com/open-telemetry/opentelemetry-python"
},
{
"type": "WEB",
"url": "https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.45.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "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",
"type": "CVSS_V4"
}
],
"summary": "OpenTelemetry Python: Unbounded memory allocation in Jaeger baggage propagation"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.