CVE-2026-50274 json
dd-trace-go: Improper parsing of W3C baggage headers may lead to DoS
published 2026-07-15 3 mo ago modified 2026-10-24 15 d ago also GHSA-74j5-xf3v-crq8 , GO-2026-6000 , EUVD-2026-45328
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/DataDog/dd-trace-go/v2 2.8.1
- govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260727T201416-160000.1.1
suse advisories SUSE-SU-2026:23216-1SUSE-SU-2026:23227-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260727T201416-160000.1.1
opensuse advisories openSUSE-SU-2026:21551-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-50274 updated cvss 7.5
github.com/DataDog/dd-trace-go: Datadog dd-trace-go: Denial of Service via malicious baggage headers
-
Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/lighthouse-agent-rhel9, rhacm2/lighthouse-coredns-rhel9 Red Hat OpenShift Container Platform 4 openshift4/ose-coredns, openshift4/ose-coredns-rhel9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/DataDog/dd-trace-go | <=1.24.1 all versions |
no fix listed |
| go | github.com/DataDog/dd-trace-go/v2 | <2.8.1 |
2.8.1 |
Affected products
- DataDog dd-trace-go
Classification
References
Sources
- CVE List CVE-2026-50274
- GitHub Advisory GHSA-74j5-xf3v-crq8
- NVD CVE-2026-50274
- OSV GO-2026-6000
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.