CVE-2026-50273: Datadog .NET Tracer: Improper parsing of W3C baggage headers may lead to DoS
DataDog · dd-trace-dotnet
Affected: DataDog dd-trace-dotnet · 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 .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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- DataDog · dd-trace-dotnet< 3.43.0
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-50273 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-dotnet/security/advisories/GHSA-38wrgithub.com
- github.com/DataDog/dd-trace-dotnet/pull/8555github.com
- github.com/DataDog/dd-trace-dotnet/commit/38092e0d41a36decbe649egithub.com
- github.com/DataDog/dd-trace-dotnet/releases/tag/v3.43.0github.com