Allocation of Resources Without Limits or Throttling Affecting linkerd2-proxy package, versions <2.362.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.3% (23rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-LINKERD2PROXY-17996074
  • published16 Jul 2026
  • disclosed17 Jul 2026

Introduced: 16 Jul 2026

CVE-2026-48504  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade Chainguard linkerd2-proxy to version 2.362.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream linkerd2-proxy package and not the linkerd2-proxy package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.