CVE-2026-40345: Deepmerge ts · DeepmergeTS has stack exhaustion when merging recursive object graphs
Affects deepmerge-tsSource GCVE Database
Not known to be exploited · CVSS 8.2 High : upgrade to 8.0.0 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.0.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by GitHub, Inc.
, 132 days before disclosure
CVE published
on cve.org
, t = 0
CISA SSVC assessment
proof of concept public
, 24 hours after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade deepmerge-ts to 8.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmdeepmerge-ts | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in deepmerge-ts version 8.0.0. Users should upgrade to version 8.0.0 or later to prevent stack exhaustion caused by recursive object graphs. Until upgraded, avoid passing recursive object graphs to the merge functions. No other mitigations are specified.
Description
The deepmerge-ts library versions prior to 8.0.0 contain a vulnerability where merging recursive object graphs can cause a stack exhaustion crash. This occurs because the merge functions do not detect cycles and recurse indefinitely when both input objects contain self-references at the same property path. This leads to a RangeError due to maximum call stack size exceeded, potentially crashing Node.js applications that process attacker-controlled recursive objects.