CVE-2026-48504 | OpenTelemetry Rust: Unbounded memory allocation in W3C Baggage propagation

OpenTelemetry Rust is the Rust OpenTelemetry implementation. In 0.32.0 and earlier, BaggagePropagator::extract_with_context in opentelemetry_sdk did not enforce W3C Baggage size limits before parsing an inbound baggage header, so a large attacker-controlled header could cause unnecessary CPU work and short-lived heap allocations while parsing entries later discarded by the SDK's baggage storage limits. Services that accept untrusted inbound propagation headers may experience increased per-request resource usage when processing oversized baggage headers. This issue is fixed in version 0.32.1.

Published: 2026-07-17 Last update: 2026-07-20 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-48504 is rated Low Risk (33.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.42%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-48504

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-07-18 0.10% 0.42% +0.32%
2 2026-06-12 0.10%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-48504

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
3.9 1.4 [email protected]

Weakness enumeration for CVE-2026-48504

GitHub Security Advisory for CVE-2026-48504

GHSA-w9wp-h8wv-79jx · Severity: medium · Ecosystem: rust — opentelemetry_sdk has unbounded memory allocation in W3C Baggage propagation

OS Trackers for CVE-2026-48504

vendor priority summary link
suse medium CVE-2026-48504 severity moderate: SUSE including 1 source package names (rustup), 8 product×package rows across 8 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS, … (8 product lines)): Known Not Affected 8. https://www.suse.com/security/cve/CVE-2026-48504/

Affected software / configurations for CVE-2026-48504

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-48504

cvelogic Threat Intelligence