https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T02:42:31.326795+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-338919 EUVD-2026-338919 2026-10-06T02:42:31.375645+00:00 EUVD-2026-338919 https://cve.radiocsirt.org/vuln/fkie_cve-2026-48504 fkie_cve-2026-48504 2026-10-06T02:42:31.375679+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-w9wp-h8wv-79jx GHSA-w9wp-h8wv-79jx — opentelemetry_sdk has unbounded memory allocation in W3C Baggage propagation 2026-10-06T02:42:31.375714+00:00

Affected: crates.io: opentelemetry_sdk

## 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 ad…