PT-2026-60363 · Datadog · Dd-Trace-Go

CVE-2026-50274

·

Published

2026-07-15

·

Updated

2026-08-10

CVSS v3.1

7.5

High

VectorAV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Name of the Vulnerable Software and Affected Versions dd-trace-go versions prior to 2.8.1
Description Datadog tracing libraries implementing W3C baggage propagation fail to enforce limits on the number of items or total bytes when parsing incoming baggage HTTP headers during the extraction process. While limits are defined by DD TRACE BAGGAGE MAX ITEMS and DD TRACE BAGGAGE MAX BYTES, they were only applied to baggage injection. A remote, unauthenticated attacker can exploit this by sending a request with a baggage header containing an excessively large number of comma-separated key-value pairs or a single oversized value. This forces the tracer to allocate a hash-map entry for each pair, leading to unbounded CPU and memory consumption, which results in a denial of service for HTTP services with baggage propagation enabled. This propagation style is enabled by default in most affected tracers.
Recommendations Update dd-trace-go to version 2.8.1 or later. Disable baggage extraction by removing baggage from the DD TRACE PROPAGATION STYLE or DD TRACE PROPAGATION STYLE EXTRACT variables. Cap the maximum HTTP request header size at an upstream proxy or web server.

Exploit

Fix

DoS

Resource Exhaustion

Allocation of Resources Without Limits

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-50274
GHSA-74J5-XF3V-CRQ8
GO-2026-6000
OPENSUSE-SU-2026:21551-1
SUSE-SU-2026:23216-1
SUSE-SU-2026:23227-1

Affected Products

Dd-Trace-Go