---
id: CVE-2026-48504
title: opentelemetry_sdk has unbounded memory allocation in W3C Baggage propagation
summary: opentelemetry_sdk has unbounded memory allocation in W3C Baggage propagation
severity: medium
cvss: 5.3
cwe:
  - CWE-770
vendor: opentelemetry_sdk
product: opentelemetry_sdk
ecosystem: rust
affected:
  - opentelemetry_sdk <= 0.32.0
patched:
  - opentelemetry_sdk 0.32.1
published: '2026-06-25'
updated: '2026-06-25'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-w9wp-h8wv-79jx'
references:
  - url: >-
      https://github.com/open-telemetry/opentelemetry-rust/security/advisories/GHSA-w9wp-h8wv-79jx
  - url: 'https://github.com/advisories/GHSA-w9wp-h8wv-79jx'
tags:
  - ghsa
  - rust
ingestedAt: '2026-06-26T16:43:14.233Z'
epss: 0.00418
epssPercentile: 0.35778
---

## Overview

## Summary

`BaggagePropagator::extract_with_context` in `opentelemetry_sdk` did not enforce the W3C Baggage size limits before parsing an inbound `baggage` header. A large attacker-controlled header could cause unnecessary CPU work and short-lived heap allocations while parsing entries that would later be discarded by the SDK's baggage storage limits.

The SDK now applies limits aligned with the W3C Baggage limits:

  - 64 list-members
  - 8192 bytes total

## Impact

Services that accept untrusted inbound propagation headers may experience increased per-request resource usage when processing oversized `baggage` headers. This can contribute to denial-of-service risk, especially when application or transport-level header limits are absent or configured above the W3C Baggage limits.
 
The impact is limited to availability. This issue does not expose telemetry data, modify telemetry data, or allow code execution.

## Patches

Upgrade `opentelemetry_sdk` to version `0.32.1` or later.

Version `0.32.1` rejects `baggage` header values larger than 8192 bytes and limits extraction to the first 64 list-members.

  ## Workarounds

If upgrading immediately is not possible, reject or limit inbound `baggage` headers larger than 8192 bytes before invoking OpenTelemetry propagation extraction. This can be enforced at a proxy, gateway, middleware layer, or custom carrier boundary.

## Resources

  - W3C Baggage limits: https://www.w3.org/TR/baggage/#limits
  - Related OpenTelemetry Java advisory: https://github.com/open-telemetry/opentelemetry-java/security/advisories/GHSA-rcgg-9c38-7xpx
  - Related OpenTelemetry Go advisory: https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475
  - CVE-2026-48504

## Credit

tonghuaroot

## Affected packages

- `opentelemetry_sdk <= 0.32.0`

## Remediation

Upgrade to a patched release:

- `opentelemetry_sdk 0.32.1`