Algorithmic Complexity Affecting node-immutable package, versions <4.3.9-1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.43% (36th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-NODEIMMUTABLE-17912075
  • published9 Jul 2026
  • disclosed8 Jul 2026

Introduced: 8 Jul 2026

CVE-2026-59880  (opens in a new tab)
CWE-407  (opens in a new tab)

How to fix?

Upgrade Debian:unstable node-immutable to version 4.3.9-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream node-immutable package and not the node-immutable package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.