What’s Vulnerable › Vulnerabilities

CVE-2026-50274: dd-trace-go: Improper parsing of W3C baggage headers may lead to DoS

• Severity: high (CVSS 7.5 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.8% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-07-17 · updated 2026-10-24
• Weakness: CWE-770

Description

Datadog dd-trace-go is a Go client library for Datadog application performance monitoring, profiling, and security monitoring. Prior to 2.8.1, Datadog tracing libraries that implement W3C baggage propagation parse incoming baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES limits on the extract path. A remote, unauthenticated attacker can send a request whose baggage header contains an arbitrarily large number of comma-separated key-value pairs or a single very large value, causing unbounded CPU and memory consumption and enabling a remote denial of service against HTTP services with baggage propagation enabled. This issue is fixed in version 2.8.1.

Affected products

• DataDog dd-trace-go: before 2.8.1

References

• https://github.com/DataDog/dd-trace-go/commit/192712ba0291b2e89166259111ebb5e90c8f52df
• https://github.com/DataDog/dd-trace-go/pull/4720
• https://github.com/DataDog/dd-trace-go/releases/tag/v2.8.1
• https://github.com/DataDog/dd-trace-go/security/advisories/GHSA-74j5-xf3v-crq8

Get alerted when CVE-2026-50274 or the next vulnerability affects your stack