Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Improper handling of W3C baggage headers in github.com/DataDog/dd-trace-go/v2 before 2.8.1, and in github.com/DataDog/dd-trace-go up to 1.24.1 (no fixed version listed), lets extraction parse baggage without item-count or size limits. A remote, unauthenticated attacker can send a request with a very large baggage header, causing unbounded CPU and memory use and a denial of service. Upgrade github.com/DataDog/dd-trace-go/v2 to 2.8.1 or later. If upgrading is not possible, remove baggage from the propagation style settings or cap HTTP request header size at an upstream proxy.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0079, the 56th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:13 UTC First seen by agentprime
- 31 Oct 2026, 14:13 UTC Confirmed by OSV