CVE-2026-50274: dd-trace-go: Improper parsing of W3C baggage headers may lead to DoS
DataDog · dd-trace-go
Affected: DataDog dd-trace-go · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 56% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- DataDog · dd-trace-go< 2.8.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
CoverageNo articles yet
No CyberSIXT article names CVE-2026-50274 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-770cwe.mitre.org
- github.com/DataDog/dd-trace-go/security/advisories/GHSA-74j5-xf3github.com
- github.com/DataDog/dd-trace-go/pull/4720github.com
- github.com/DataDog/dd-trace-go/commit/192712ba0291b2e89166259111github.com
- github.com/DataDog/dd-trace-go/releases/tag/v2.8.1github.com