Immutable.js provides many Persistent Immutable data structures. Prior to 4.3.9 and 5.1.8, List#set, List#setSize, List#setIn, List#updateIn, and the functional set, setIn, and updateIn mishandle an index or size in the range 2 30 to 2 31 in setListBounds in src/List.js, causing an empty List to enter an uncatchable infinite loop, a populated List to allocate without bound until process abort, or setSize to silently wrap large values. This issue is fixed in versions 4.3.9 and 5.1.8.
CVE-2026-59879
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 21.9%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 10, 2026
Advisory Details (5)
Auto-updated Jul 8, 2026Immutable.js `List` 32-bit trie overflow → unrecoverable DoS · Advisory · immutable-js/immutable-js · GitHub
https://github.com/immutable-js/immutable-js/security/advisories/GHSA-v56q-mh7h-f735v5.1.8
Patch available: immutable-js/immutable-js v5.1.8
https://github.com/immutable-js/immutable-js/releases/tag/v5.1.8v4.3.9
Patch available: immutable-js/immutable-js v4.3.9
https://github.com/immutable-js/immutable-js/releases/tag/v4.3.9commit f0bc997d8eb9 (immutable-js/immutable-js)
Patch available: immutable-js/immutable-js v4.3.9 (contains commit f0bc997d8eb9)
https://github.com/immutable-js/immutable-js/commit/f0bc997d8eb9886aff2236635aa210a95a04304acommit a1a1ee412dca (immutable-js/immutable-js)
Patch available: immutable-js/immutable-js v5.1.8 (contains commit a1a1ee412dca)
https://github.com/immutable-js/immutable-js/commit/a1a1ee412dcaa380ab325196283d06594ffe4b84Weakness Classification(4)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-11 17:28 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 05:18 UTCEG score recompute▼ 1.20
- 2026-07-10 20:19 UTCNVD updateCVSS v3 → 7.5
- 2026-07-10 17:08 UTCEG score recompute
- 2026-07-10 04:56 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 16:45 UTCEG score recompute
- 2026-07-09 04:35 UTCEG score recompute
- 2026-07-08 16:24 UTCEG score recompute
- 2026-07-08 16:24 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-59879?
When was CVE-2026-59879 disclosed?
Is CVE-2026-59879 actively exploited?
What is the CVSS score of CVE-2026-59879?
How do I remediate CVE-2026-59879?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59879
Is Your Infrastructure Affected by CVE-2026-59879?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.