Is CVE-2026-50272 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-50272 being exploited in the wild.

How severe is CVE-2026-50272?

High severity, with a CVSS score of 7.5, published 17 July 2026.

Which products and versions are affected?

Datadog Dd-Trace-Js < 5.100.0; dd-trace (npm) < 5.100.0, SEMVER:introduced=0,fixed=5.100.0.

Is there a fix for CVE-2026-50272?

Yes. dd-trace (npm): upgrade to 5.100.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-50272 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-50272?

Check whether you run Datadog Dd-Trace-Js or dd-trace (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-50272: DataDog dd-trace-js denial of service via unbounded baggage extraction

Q: Which products and versions are affected?

Datadog Dd-Trace-Js < 5.100.0; dd-trace (npm) < 5.100.0, SEMVER:introduced=0,fixed=5.100.0.

Q: Is there a fix for CVE-2026-50272?

Yes. dd-trace (npm): upgrade to 5.100.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-50272 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-50272?

Check whether you run Datadog Dd-Trace-Js or dd-trace (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-50272 · Severity: high · CVSS 7.5 · Published 2026-07-17

Datadog's dd-trace library for Node.js, which is used to monitor application performance, contains a vulnerability that can be used to crash services. An attacker can send specially crafted web requests with excessively large headers that the library fails to limit. This results in the application consuming all available memory and processor power, leading to a service outage.

Vendors: Datadog, npm.

Quick answers

Is CVE-2026-50272 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50272 being exploited in the wild.
How severe is CVE-2026-50272?: High severity, with a CVSS score of 7.5, published 17 July 2026.
Which products and versions are affected?: Datadog Dd-Trace-Js < 5.100.0; dd-trace (npm) < 5.100.0, SEMVER:introduced=0,fixed=5.100.0.
Is there a fix for CVE-2026-50272?: Yes. dd-trace (npm): upgrade to 5.100.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-50272 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-50272?: Check whether you run Datadog Dd-Trace-Js or dd-trace (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

dd-trace (npm): upgrade to 5.100.0 or later
```
npm install dd-trace@5.100.0
```

Technical details

A resource exhaustion vulnerability exists in dd-trace-js prior to version 5.100.0. The W3C baggage propagation logic in `packages/dd-trace/src/baggage.js` and `packages/dd-trace/src/opentracing/propagation/text_map.js` parses incoming HTTP headers without enforcing the `DD_TRACE_BAGGAGE_MAX_ITEMS` or `DD_TRACE_BAGGAGE_MAX_BYTES` limits during the extraction phase. A remote, unauthenticated attacker can provide a baggage header with an arbitrarily large number of key-value pairs or extremely large values. This causes unbounded CPU and memory consumption, leading to a Denial of Service (DoS). The issue is resolved in version 5.100.0 by mirroring the injection-side caps during extraction.

Affected products

DataDog dd-trace-js < 5.100.0

Identifiers

CVE-2026-50272
GHSA-wxqq-gcq8-c443

Timeline

2026-05-04: patched: Fix merged in PR #8255 and released in v5.100.0
2026-07-17: disclosed: CVE-2026-50272 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.