Skip to main content
VulnerabilityPublished Updated

CVE-2026-50275: DataDog dd-trace-php · Unthrottled Resource Allocation

Affects DataDog dd-trace-phpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.19.2 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.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.19.2
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-php and datadog/dd-trace-php to 1.19.2.

Affected software

ProductAffectedFixed in
DataDogdd-trace-phpAffected
  • <1.19.2
Fixed in
  • 1.19.2
GitHubdatadog/dd-trace-phppkg:github/datadog/dd-trace-phpOther threatsAffected
  • <1.19.2
Fixed in
  • 1.19.2

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-php to version 1.19.2 or later, where this issue is fixed. Alternatively, disable baggage extraction by removing baggage from DD_TRACE_PROPAGATION_STYLE or DD_TRACE_PROPAGATION_STYLE_EXTRACT to mitigate the risk. No other mitigations are specified.

Description

CVE-2026-50275 is a high-severity vulnerability in DataDog's dd-trace-php library prior to version 1.19.2. It involves the ddtrace_deserialize_baggage function parsing incoming W3C baggage HTTP headers without enforcing limits on the number or size of key-value pairs. This allows a remote unauthenticated attacker to cause unbounded CPU and memory consumption by sending large or numerous baggage items. The issue is fixed in version 1.19.2.

References

Community reviews

Loading reviews…