Skip to main content
VulnerabilityPublished Updated

CVE-2026-50277: DataDog dd-trace-cpp · Unthrottled Resource Allocation

Affects DataDog dd-trace-cppSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2.1.0 soon.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade dd-trace-cpp and datadog/dd-trace-cpp to 2.1.0.

Affected software

ProductAffectedFixed in
DataDogdd-trace-cppAffected
  • <2.1.0
Fixed in
  • 2.1.0
GitHubdatadog/dd-trace-cpppkg:github/datadog/dd-trace-cppOther threatsAffected
  • <2.1.0
Fixed in
  • 2.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade dd-trace-cpp to version 2.1.0 or later, where the issue is fixed by enforcing baggage size and item count limits during extraction. Until upgraded, consider disabling baggage extraction by removing baggage from DD_TRACE_PROPAGATION_STYLE or DD_TRACE_PROPAGATION_STYLE_EXTRACT to reduce exposure.

Description

dd-trace-cpp is the Datadog distributed tracing library for C++. Prior to 2.1.0, dd-trace-cpp parses incoming W3C baggage headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES on the extraction path, even though those limits are enforced during injection. A remote unauthenticated attacker can send a header containing many comma-separated key-value pairs or one very large value, causing per-request hash-map allocation and unbounded CPU and memory consumption. Baggage extraction is enabled by default in most affected tracers unless baggage is removed from DD_TRACE_PROPAGATION_STYLE or DD_TRACE_PROPAGATION_STYLE_EXTRACT, so affected internet-facing services can be denied service. This issue is fixed in version 2.1.0.

References

Community reviews

Loading reviews…