Vulnerabilities in pkg:nuget/Datadog.Trace
PACKAGECVE-2026-50273 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting dd-trace-dotnet libraries in the NuGet ecosystem. The issue involves improper parsing of w3c baggage headers may lead to dos. Remediation is available by upgrading affected packages to version 3.43.0.
pkg:nuget/Datadog.Trace
Vulnerability advisories affecting package pkg:nuget/Datadog.Trace. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-38wr-vpc7-2mp4 | CVE-2026-50273 | HIGH | dd-trace-dotnet: Improper parsing of W3C baggage headers may lead to DoS |
CVE-2026-50273 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2026-50273
To remediate this vulnerability, upgrade all affected dd-trace-dotnet dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade Datadog.Trace to 3.43.0
Upgrade Datadog.Trace.OpenTracing to 3.43.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for Datadog.Trace
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-50273, inspect your project dependencies for dd-trace-dotnet:
inspect dependencies for Datadog.Trace
Analyze the terminal output to locate any version of dd-trace-dotnet in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.43.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In dd-trace-dotnet, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-50273 Affected dd-trace-dotnet Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
Datadog.Trace
|
NuGet |
< 3.43.0
|
3.43.0
|
|
Datadog.Trace.OpenTracing
|
NuGet |
< 3.43.0
|
3.43.0
|
References
Frequently Asked Questions
What is CVE-2026-50273?
Which dd-trace-dotnet versions are affected?
What version fixes CVE-2026-50273?
Is Datadog.Trace affected?
Is Datadog.Trace.OpenTracing affected?
What is the CVSS score of CVE-2026-50273?
What CWE is associated with CVE-2026-50273?
How can I check NuGet dependencies for CVE-2026-50273?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-38wr-vpc7-2mp4",
"modified" : "2026-07-15T22:59:30Z",
"published" : "2026-07-15T22:59:30Z",
"aliases" : [ "CVE-2026-50273" ],
"summary" : "dd-trace-dotnet: Improper parsing of W3C baggage headers may lead to DoS",
"details" : "### Impact\nDatadog tracing libraries that implement W3C baggage propagation parse incoming baggage HTTP headers without enforcing item-count or byte-size limits on the extract path. The DD_TRACE_BAGGAGE_MAX_ITEMS (default 64) and DD_TRACE_BAGGAGE_MAX_BYTES (default 8192) limits were applied only to baggage injection, not extraction. 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). The tracer allocates a hash-map entry for each pair on every request, causing unbounded CPU and memory consumption and enabling a remote Denial of Service against any HTTP service that has the baggage propagation style enabled.\nThe baggage propagation style is enabled by default in most affected tracers, so any internet-facing service that has been instrumented with an affected tracer version is exposed unless the propagation style has been explicitly narrowed.\n\n\n### Patches\nThis is resolved in version 3.43.0 and later of the `dd-trace-dotnet` library.\n\n### Workarounds\nIf users cannot upgrade immediately:\n1. Disable `baggage` extraction by removing `baggage` from `DD_TRACE_PROPAGATION_STYLE` (or `DD_TRACE_PROPAGATION_STYLE_EXTRACT` if set independently).\n2. Cap the maximum HTTP request header size at an upstream proxy or web server (for example, Apache `LimitRequestFieldSize`, Nginx `large_client_header_buffers`, Envoy `max_request_headers_kb`).\n\n### Resources\nRelated upstream advisories:\n[opentelemetry-go GHSA-mh2q-q3fh-2475](https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475)\n[opentelemetry-dotnet GHSA-g94r-2vxg-569j](https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-g94r-2vxg-569j)",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "NuGet",
"name" : "Datadog.Trace"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.43.0"
} ]
} ]
}, {
"package" : {
"ecosystem" : "NuGet",
"name" : "Datadog.Trace.OpenTracing"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.43.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/DataDog/dd-trace-dotnet/security/advisories/GHSA-38wr-vpc7-2mp4"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/DataDog/dd-trace-dotnet"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-400", "CWE-770" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-15T22:59:30Z",
"nvd_published_at" : null
}
}