CVE-2026-128086
CVE
Medium
· CVSS 5.3
Medium Impacttelemetry/opentelemetry: Memory Amplification via Dense W3C Baggage Properties
Exploitable under specific conditions
This vulnerability can affect KrakenD under specific conditions. Review the affected versions below and upgrade if your deployment is exposed.
telemetry/opentelemetry is enabled with propagation on, its
default. KrakenD extracts the baggage header of every request at the service level,
before any authentication, so an unauthenticated client can send it to any endpoint
except those listed in skip_paths. Until you upgrade, set disable_propagation to
true under layers.global, or set the environment variable
OTEL_PROPAGATORS=tracecontext to keep trace propagation and drop baggage.Component
OpenTelemetry-Go (baggage propagation)
Disclosed
Nov 19, 2026
CVSS Score
5.3
Description
baggage header by turning every property of every
member into its own object up front, then copies and serializes them again. A header
that stays within the size limits but packs thousands of properties makes each parse
allocate around 95 times its own size, about 778 KB for an 8 KB header. A client
repeating such requests puts the process under heavy allocation and garbage collection
pressure, degrading its performance. Affects OpenTelemetry-Go from 1.0.0-RC1 up to
1.46.x. Fixed in 1.47.0.Version summary
Community Edition
3.0.5
addresses this advisory
Affected CE versions
>= 2.0, < 3.0.5
Enterprise Edition
3.0.5, 2.13.15
addresses this advisory
Affected EE versions
>= 2.0, < 2.13.15 || >= 3.0, < 3.0.5
Upgrade to the addressed version or later to remediate this vulnerability.