CVE-2026-50273 Datadog .NET Tracer: Improper parsing of W3C baggage headers may lead to DoS
Remote attackers can cause denial of service in .NET applications using Datadog Tracer by sending oversized W3C baggage headers, bypassing resource limits.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-50273?
CVE-2026-50273 is a high-severity denial of service vulnerability in DataDog dd-trace-dotnet, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Datadog .NET Tracer is a client library for Datadog APM for .NET applications. Prior to 3.43.0, 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 on extraction, allowing a remote unauthenticated attacker to send a baggage header with many comma-separated key-value pairs or one very large value and cause unbounded CPU and memory consumption in services with baggage propagation enabled. This issue is fixed in version 3.43.0.
Weakness: CWE-770
Which versions are affected by CVE-2026-50273?
4 open source packages ship an affected version, including Datadog.Trace and Datadog.Trace.OpenTracing.
| Package | Affected | Fixed in |
|---|---|---|
Datadog.Trace NuGet | All versions | 3.43.0 |
Datadog.Trace NuGet | All versions | 3.43.0 |
Datadog.Trace.OpenTracing NuGet | All versions | 3.43.0 |
Datadog.Trace.OpenTracing NuGet | All versions | 3.43.0 |
How do I fix CVE-2026-50273?
Upgrade Datadog.Trace to 3.43.0 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-50273 being exploited?
There is no known exploitation of CVE-2026-50273 in the wild and no public exploit code.
Sources
Also known as GHSA-38wr-vpc7-2mp4.