{"answers":{"affected":"6 open source packages ship an affected version, including immutable. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59880 exists.","fix":"Upgrade immutable to a fixed version for your release line: 3.8.4, 4.3.9 or 5.1.8.","what":"CVE-2026-59880 is a high-severity denial of service vulnerability in immutable-js, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-59880 and fix it if it is affected.\n\nWhat it is: CVE-2026-59880 is a high-severity denial of service vulnerability in immutable-js, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59880 exists.\n\nAffected packages and fixed versions:\n- immutable (npm): affected all versions; fixed in 3.8.4\n- immutable (npm): affected all versions; fixed in 3.8.4\n- immutable (npm): affected from 4.0.0-beta.1; fixed in 4.3.9\n- immutable (npm): affected from 4.0.0-beta.1; fixed in 4.3.9\n- immutable (npm): affected from 5.0.0-beta.1; fixed in 5.1.8\n- immutable (npm): affected from 5.0.0-beta.1; fixed in 5.1.8\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59880/ (Markdown: https://insights.sbomify.com/CVE-2026-59880/index.md)","id":"CVE-2026-59880","markdown":"https://insights.sbomify.com/CVE-2026-59880/index.md","name":"CVE-2026-59880","record":{"aliases":["CLEANSTART-2026-BI32681","CLEANSTART-2026-VB50849","CLSA-2026-1784769617","CLSA-2026-1784856200","CLSA-2026-1784856463","CLSA-2026-1784943220","CLSA-2026-1784943293","DEBIAN-CVE-2026-59880","ECHO-bbb2-861f-196e","GHSA-xvcm-6775-5m9r","MINI-2w6v-xm84-fqgx","MINI-33qf-356q-pj3q","MINI-43q8-37cx-hp5v","MINI-684m-67gh-32mx","MINI-75ch-37wf-5p2p","MINI-fgw7-7475-mcvr","MINI-m4v4-74jh-8v46","MINI-wwrj-p338-6w5j","ROOT-APP-NPM-CVE-2026-59880","UBUNTU-CVE-2026-59880"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript immutable library","requires_auth":"none","summary":"Attackers can cause CPU exhaustion in Immutable.js applications by inserting keys with colliding hashes into Maps or Sets.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"immutable","vendor":"immutable-js"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Immutable.js: Hash-collision algorithmic complexity denial of service in Immutable.Map/Set","id":"CVE-2026-59880","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":6,"n_references":5,"next":{"headline":"AIOHTTP: WebSocket client accepts compressed frames without negotiated permessage-deflate","id":"CVE-2026-59881"},"packages":[{"ecosystem":"npm","fixed":["3.8.4"],"introduced":["0"],"last_affected":[],"package":"immutable","purl":null,"source":"GHSA-xvcm-6775-5m9r"},{"ecosystem":"npm","fixed":["3.8.4"],"introduced":["0"],"last_affected":[],"package":"immutable","purl":"pkg:npm/immutable","source":"GHSA-xvcm-6775-5m9r"},{"ecosystem":"npm","fixed":["4.3.9"],"introduced":["4.0.0-beta.1"],"last_affected":[],"package":"immutable","purl":null,"source":"GHSA-xvcm-6775-5m9r"},{"ecosystem":"npm","fixed":["4.3.9"],"introduced":["4.0.0-beta.1"],"last_affected":[],"package":"immutable","purl":"pkg:npm/immutable","source":"GHSA-xvcm-6775-5m9r"},{"ecosystem":"npm","fixed":["5.1.8"],"introduced":["5.0.0-beta.1"],"last_affected":[],"package":"immutable","purl":null,"source":"GHSA-xvcm-6775-5m9r"},{"ecosystem":"npm","fixed":["5.1.8"],"introduced":["5.0.0-beta.1"],"last_affected":[],"package":"immutable","purl":"pkg:npm/immutable","source":"GHSA-xvcm-6775-5m9r"}],"prev":{"headline":"Immutable.js `List` 32-bit trie overflow → unrecoverable DoS","id":"CVE-2026-59879"},"products":["immutable-js"],"published":"2026-07-08","related":[{"cvss_score":8.7,"headline":"Immutable.js `List` 32-bit trie overflow → unrecoverable DoS","id":"CVE-2026-59879","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":8.7,"headline":"Immutable.js: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in immutable","id":"CVE-2026-29063","kev_date_added":null,"published":"2026-03-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-08","vendors":["immutable-js"]},"summary":"Attackers can cause CPU exhaustion in Immutable.js applications by inserting keys with colliding hashes into Maps or Sets.","url":"https://insights.sbomify.com/CVE-2026-59880/"}