ubuntu-cve-2026-59880
Vulnerability from osv_ubuntu
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": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-immutable",
"binary_version": "3.8.2+dfsg-3"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "node-immutable",
"purl": "pkg:deb/ubuntu/node-immutable@3.8.2+dfsg-3?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.8.2+dfsg-3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-immutable",
"binary_version": "4.0.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "node-immutable",
"purl": "pkg:deb/ubuntu/node-immutable@4.0.0-2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.8.2+dfsg-3",
"4.0.0-1",
"4.0.0-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-immutable",
"binary_version": "4.3.4-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "node-immutable",
"purl": "pkg:deb/ubuntu/node-immutable@4.3.4-1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.1.0-3",
"4.3.4-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-immutable",
"binary_version": "4.3.4-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "node-immutable",
"purl": "pkg:deb/ubuntu/node-immutable@4.3.4-1?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.3.4-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-immutable",
"binary_version": "4.3.8-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "node-immutable",
"purl": "pkg:deb/ubuntu/node-immutable@4.3.8-2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.3.4-1",
"4.3.8-2"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2026-59880",
"modified": "2026-07-15T17:53:45Z",
"published": "2026-07-08T16:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-59880"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59880"
},
{
"type": "REPORT",
"url": "https://github.com/immutable-js/immutable-js/security/advisories/GHSA-xvcm-6775-5m9r"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "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",
"type": "CVSS_V4"
},
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-59880"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.