Allocation of Resources Without Limits or Throttling Affecting datadog.trace.opentracing package, versions [3.5.0,3.43.0)


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.48% (39th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DOTNET-DATADOGTRACEOPENTRACING-18687304
  • published12 Aug 2026
  • disclosed15 Jul 2026
  • creditUnknown

Introduced: 15 Jul 2026

CVE-2026-50273  (opens in a new tab)
CWE-400  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade Datadog.Trace.OpenTracing to version 3.43.0 or higher.

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through improper parsing of W3C baggage headers in the extraction process. An attacker can exhaust system resources by sending HTTP requests with a large number of comma-separated key-value pairs or a single excessively large value in the baggage header, resulting in unbounded CPU and memory consumption. This is only exploitable if baggage propagation style is enabled, which is the default in most affected configurations.

Workaround

This vulnerability can be mitigated by disabling baggage extraction via configuration or by capping the maximum HTTP request header size at an upstream proxy or web server.

References

CVSS Base Scores

version 4.0
version 3.1