CVE-2026-50273

Datadog .NET Tracer: Improper parsing of W3C baggage headers may lead to DoS

Published Jul 17, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Datadog .NET Tracer is a client library that sends and receives tracing data for .NET applications. Prior to version 3.43.0, the library parsed incoming W3C baggage HTTP headers without enforcing the maximum item or byte limits defined by DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES. This omission allows an unauthenticated remote attacker to supply a header containing a large number of comma‑separated key‑value pairs or a single very large value, causing the tracer to consume unbounded CPU and memory during parsing. The result is that any .NET service with baggage propagation enabled can suffer a denial of service. The vendor addressed the issue in release 3.43.0.

Affected Systems

The issue affects the DataDog dd‑trace‑dotnet library in all versions prior to 3.43.0 when baggage propagation is configured. Any .NET application that employs this tracer with baggage enabled is at risk.

Risk and Exploitability

The CVSS score of 7.5 classifies the issue as high severity, while the EPSS score of less than 1% indicates a low likelihood of widespread exploitation at present. The vulnerability is not listed in CISA’s KEV catalog. A remote unauthenticated attacker can trigger the exploit by sending a crafted HTTP request containing a large baggage header, a path that is inferred from the description as the most likely attack vector.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Datadog dd‑trace‑dotnet library to version 3.43.0 or newer to apply the vendor‑provided fix.
  • If an immediate upgrade is not feasible, disable baggage propagation in the tracer configuration or enforce custom limits on the incoming baggage header before it reaches the library.
  • Configure application‑level monitoring or request filtering to detect unusually large HTTP headers and block or rate‑limit such requests to prevent resource exhaustion.

Generated by OpenCVE AI on July 30, 2026 at 23:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-38wr-vpc7-2mp4 dd-trace-dotnet: Improper parsing of W3C baggage headers may lead to DoS
History
Type Values Removed Values Added
First Time appeared Datadog
Datadog dd-trace-dotnet
Vendors & Products Datadog
Datadog dd-trace-dotnet
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Datadog .NET Tracer: Improper parsing of W3C baggage headers may lead to DoS
Weaknesses CWE-770
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 17, 2026, 7:46 PM
Reserved
Jun 4, 2026, 4:26 PM
Status
Awaiting Analysis
Published
Jul 17, 2026, 6:17 PM
Modified
Oct 24, 2026, 8:10 PM