Description
Immutable.js provides many Persistent Immutable data structures. Prior to 4.3.9 and 5.1.8, Immutable.Map and Immutable.Set keep keys that share the same 32-bit hash in a HashCollisionNode collision bucket that is scanned linearly, allowing an attacker who controls keys inserted into a Map, such as through Immutable.Map(obj), Immutable.fromJS(obj), state.merge(userObject), or mergeDeep, to craft many colliding keys and degrade insertion and lookup to consume disproportionate CPU. This issue is fixed in versions 4.3.9 and 5.1.8.
Affected products
immutable-js: immutable
References6
- github.com/immutable-js/immutable-js/security/advisories/GHSA-x… ExploitMitigationVendor Advisory
- github.com/immutable-js/immutable-js/security/advisories/GHSA-x… ExploitMitigationVendor Advisory
- github.com/immutable-js/immutable-js/commit/3dd7e5655012597a418… Patch
- github.com/immutable-js/immutable-js/commit/e51d49fc612ded5ec4d… Patch
- github.com/immutable-js/immutable-js/releases/tag/v4.3.9 Release Notes
- github.com/immutable-js/immutable-js/releases/tag/v5.1.8 Release Notes
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - CVSS 4.0
-
8.7
HIGH
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 1% percentile: 52 · as of 15 November 2026
- CWE
- CWE-407
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.