CVE-2026-50273: dd-trace-dotnet · Improper parsing of W3C baggage headers may lead to DoS
Affects Datadog.TraceSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 3.43.0 soon.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.43.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Datadog.Trace and Datadog.Trace.OpenTracing to 3.43.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NuGetDatadog.Trace | Affected
| Fixed in
|
| NuGetDatadog.Trace.OpenTracing | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to dd-trace-dotnet version 3.43.0 or later, where this issue is resolved. If immediate upgrade is not possible, mitigate by disabling baggage extraction via configuration (removing 'baggage' from DD_TRACE_PROPAGATION_STYLE or DD_TRACE_PROPAGATION_STYLE_EXTRACT). Additionally, limit the maximum HTTP request header size at upstream proxies or web servers using settings such as Apache's LimitRequestFieldSize, Nginx's large_client_header_buffers, or Envoy's max_request_headers_kb.
Description
Datadog's dd-trace-dotnet library versions prior to 3.43.0 improperly parse W3C baggage HTTP headers without enforcing limits on the number or size of items during extraction. This allows a remote unauthenticated attacker to send requests with excessively large or numerous baggage items, causing unbounded CPU and memory consumption. This can lead to a denial of service (DoS) on any HTTP service using the affected tracer with baggage propagation enabled by default.
References
- github.com/DataDog/dd-trace-dotnet/security/advisories/GHSA-38wr-vpc7-2mp4 (opens in a new tab)
- github.com/DataDog/dd-trace-dotnet (opens in a new tab)
- github.com/DataDog/dd-trace-dotnet/commit/38092e0d41a36decbe649e048e48ae1b1607292f (opens in a new tab)
- github.com/DataDog/dd-trace-dotnet/pull/8555 (opens in a new tab)
- github.com/DataDog/dd-trace-dotnet/releases/tag/v3.43.0 (opens in a new tab)