CVE-2026-45292: opentelemetry-java: Unbounded Memory Allocation in W3C Baggage Propagation
opentelemetry-java is the Java implementation of the OpenTelemetry API for recording telemetry, and SDK for managing telemetry recorded by the API. Prior to 1.62.0, a vulnerability affects the baggage propagation implementation in opentelemetry-api and opentelemetry-extension-trace-propagators. Parsing oversized baggage causes unbounded memory allocation and CPU consumption. Because baggage is automatically re-injected into every outgoing request, the effect can fan out to downstream services that never received the original malicious request. This vulnerability is fixed in 1.62.0.
Security readout for executives and security teams
Plain-English summary
A flaw in the OpenTelemetry Java library lets an attacker send an oversized "baggage" header that forces the receiving service to burn excessive memory and CPU. Because OpenTelemetry automatically forwards baggage to downstream services, one bad request can degrade several internal systems at once, creating a denial-of-service risk across the observability path.
Executive priority
Treat as a high-priority patch for any Java estate using OpenTelemetry. The fan-out behavior means one bad request can degrade multiple internal services, so schedule upgrades within the next standard patch cycle and validate vendor products such as Red Hat middleware are updated.
Technical view
Versions of opentelemetry-java prior to 1.62.0 parse W3C baggage without size limits in opentelemetry-api and opentelemetry-extension-trace-propagators. Oversized baggage triggers unbounded allocation and CPU load (CWE-770). Because baggage is re-injected into outgoing requests, a single malicious header propagates to downstream callers. Fixed in 1.62.0 per the OpenTelemetry GHSA-rcgg-9c38-7xpx advisory and PR #8380.
Likely exposure
Java services using opentelemetry-api or the trace propagators extension below 1.62.0, especially internet-facing HTTP or gRPC endpoints that accept baggage headers and forward calls to internal services with the same instrumentation.
Exploitation context
CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N/A:H) reflects unauthenticated, network-reachable availability impact. Not listed in CISA KEV and no public reports of active exploitation in the cited sources. Red Hat has issued advisories RHSA-2026:28573 and RHSA-2026:36820 covering affected products.
Researcher notes
Root cause is missing input validation on W3C baggage parsing (CWE-770). Fix commit 03837d3c1763bc35464aea1078671e2ef2336a5f introduces bounds during parsing. Because baggage is automatically re-injected outbound, exposure extends beyond the direct receiver; map propagation paths across services when scoping. No public PoC or KEV entry in the cited sources as of the CVE update on 2026-07-10.
Mitigation direction
Upgrade opentelemetry-api and opentelemetry-extension-trace-propagators to 1.62.0 or later across all Java services.
Apply Red Hat errata RHSA-2026:28573 and RHSA-2026:36820 on impacted OpenShift and middleware products.
At edge proxies, enforce strict size limits on the baggage HTTP header for inbound traffic.
Audit downstream services for the same vulnerable versions since baggage propagates automatically.
Monitor JVM heap and CPU on telemetry-enabled services for anomalous spikes tied to inbound baggage.
Track vendor SBOMs and dependency scans for transitive pulls of the vulnerable coordinates.
Validation and detection
Run dependency scans (Maven, Gradle, Syft) for io.opentelemetry:opentelemetry-api and opentelemetry-extension-trace-propagators below 1.62.0.
Confirm remediation by verifying pinned versions in build files and container image SBOMs post-deploy.
Review GHSA-rcgg-9c38-7xpx and PR #8380 to understand the parser change and expected behavior after upgrade.
Check Red Hat CSAF VEX and RHBZ#2482785 for product-specific fix state.
Load-test a staging endpoint with large baggage headers to confirm bounded resource use after patching.
Review APM and gateway logs for oversized baggage headers as a hunting signal.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
ADP timelineredhat-SADP
Made public.
May 28, 2026, 16:37 UTC (UTC+00:00)
CVE publishedCVE Program
The CVE record was published.
May 28, 2026, 16:37 UTC (UTC+00:00)
ADP timelineredhat-SADP
Reported to Red Hat.
May 28, 2026, 17:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Jul 10, 2026, 12:05 UTC (UTC+00:00)
ADP provider summaries
CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPopentelemetry-java: opentelemetry-api: opentelemetry-extension-trace-propagators: OpenTelemetry Java: Denial of Service due to unbounded memory allocation when parsing oversized baggage