{"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-59879 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-59879 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-59879 and fix it if it is affected.\n\nWhat it is: CVE-2026-59879 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-59879 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-rc.1; fixed in 4.3.9\n- immutable (npm): affected from 4.0.0-rc.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-59879/ (Markdown: https://insights.sbomify.com/CVE-2026-59879/index.md)","id":"CVE-2026-59879","markdown":"https://insights.sbomify.com/CVE-2026-59879/index.md","name":"CVE-2026-59879","record":{"aliases":["CLEANSTART-2026-BB25914","CLEANSTART-2026-PW50490","CLSA-2026-1784682983","CLSA-2026-1784683091","CLSA-2026-1784769532","CLSA-2026-1788775607","CLSA-2026-1790866103","DEBIAN-CVE-2026-59879","ECHO-5345-cd12-bd9a","GHSA-v56q-mh7h-f735","MINI-27pm-8rf7-qgqw","MINI-29v8-g8cc-h688","MINI-64vr-hg44-phx3","MINI-8wp5-wmh6-wf64","MINI-fw5c-7cwj-g29j","MINI-gg32-4fm2-85xv","MINI-vj5g-gwrf-q5vh","MINI-x39j-2q32-rvhm","ROOT-APP-NPM-CVE-2026-59879","UBUNTU-CVE-2026-59879"],"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 denial of service via infinite loops or memory exhaustion in Immutable.js List operations using specific large indices.","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-835","name":"Loop with Unreachable Exit Condition"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"},{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"}],"description":"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.","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 `List` 32-bit trie overflow → unrecoverable DoS","id":"CVE-2026-59879","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":"Immutable.js: Hash-collision algorithmic complexity denial of service in Immutable.Map/Set","id":"CVE-2026-59880"},"packages":[{"ecosystem":"npm","fixed":["3.8.4"],"introduced":["0"],"last_affected":[],"package":"immutable","purl":null,"source":"GHSA-v56q-mh7h-f735"},{"ecosystem":"npm","fixed":["3.8.4"],"introduced":["0"],"last_affected":[],"package":"immutable","purl":"pkg:npm/immutable","source":"GHSA-v56q-mh7h-f735"},{"ecosystem":"npm","fixed":["4.3.9"],"introduced":["4.0.0-rc.1"],"last_affected":[],"package":"immutable","purl":null,"source":"GHSA-v56q-mh7h-f735"},{"ecosystem":"npm","fixed":["4.3.9"],"introduced":["4.0.0-rc.1"],"last_affected":[],"package":"immutable","purl":"pkg:npm/immutable","source":"GHSA-v56q-mh7h-f735"},{"ecosystem":"npm","fixed":["5.1.8"],"introduced":["5.0.0-beta.1"],"last_affected":[],"package":"immutable","purl":null,"source":"GHSA-v56q-mh7h-f735"},{"ecosystem":"npm","fixed":["5.1.8"],"introduced":["5.0.0-beta.1"],"last_affected":[],"package":"immutable","purl":"pkg:npm/immutable","source":"GHSA-v56q-mh7h-f735"}],"prev":{"headline":"Denial of service in Apache ActiveMQ","id":"CVE-2026-59878"},"products":["immutable-js"],"published":"2026-07-08","related":[{"cvss_score":8.7,"headline":"Immutable.js: Hash-collision algorithmic complexity denial of service in Immutable.Map/Set","id":"CVE-2026-59880","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 denial of service via infinite loops or memory exhaustion in Immutable.js List operations using specific large indices.","url":"https://insights.sbomify.com/CVE-2026-59879/"}