{"answers":{"affected":"2 open source packages ship an affected version, including js-yaml. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59868 exists.","fix":"Upgrade js-yaml to 5.2.0 or later.","what":"CVE-2026-59868 is a medium-severity denial of service vulnerability in nodeca js-yaml, 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-59868 and fix it if it is affected.\n\nWhat it is: CVE-2026-59868 is a medium-severity denial of service vulnerability in nodeca js-yaml, 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-59868 exists.\n\nAffected packages and fixed versions:\n- js-yaml (npm): affected from 5.0.0; fixed in 5.2.0\n- js-yaml (npm): affected from 5.0.0; fixed in 5.2.0\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-59868/ (Markdown: https://insights.sbomify.com/CVE-2026-59868/index.md)","id":"CVE-2026-59868","markdown":"https://insights.sbomify.com/CVE-2026-59868/index.md","name":"CVE-2026-59868","record":{"aliases":["CLSA-2026-1784596307","GHSA-g796-fgmg-93mv","UBUNTU-CVE-2026-59868"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript YAML parser","requires_auth":"none","summary":"Attackers can cause excessive CPU consumption via crafted YAML merge keys, leading to denial of service in applications using the js-yaml library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"js-yaml","vendor":"nodeca"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"}],"description":"js-yaml is a JavaScript YAML parser and dumper. From 5.0.0 before 5.2.0, when merge keys are enabled, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in version 5.2.0.","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":"js-yaml: YAML merge-key chains can force quadratic CPU consumption","id":"CVE-2026-59868","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"js-yaml: YAML merge-key chains can force quadratic CPU consumption","id":"CVE-2026-59869"},"packages":[{"ecosystem":"npm","fixed":["5.2.0"],"introduced":["5.0.0"],"last_affected":[],"package":"js-yaml","purl":null,"source":"GHSA-g796-fgmg-93mv"},{"ecosystem":"npm","fixed":["5.2.0"],"introduced":["5.0.0"],"last_affected":[],"package":"js-yaml","purl":"pkg:npm/js-yaml","source":"GHSA-g796-fgmg-93mv"}],"prev":{"headline":"Kiota: Generation-time SSRF + remote/local file inclusion via unrestricted $ref","id":"CVE-2026-59867"},"products":["js-yaml"],"published":"2026-07-08","related":[{"cvss_score":7.5,"headline":"js-yaml: YAML merge-key chains can force quadratic CPU consumption","id":"CVE-2026-59869","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":7.5,"headline":"js-yaml quadratic-complexity denial of service via YAML11_SCHEMA !!omap parsing","id":"CVE-2026-59870","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":6.8,"headline":"Deserialization Code Execution in js-yaml","id":"CVE-2013-4660","kev_date_added":null,"published":"2013-06-28"},{"cvss_score":5.3,"headline":"js-yaml: Quadratic-complexity DoS in merge key handling via repeated aliases","id":"CVE-2026-53550","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":5.3,"headline":"js-yaml has prototype pollution in merge (\u003c\u003c)","id":"CVE-2025-64718","kev_date_added":null,"published":"2025-11-13"}],"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-09","vendors":["nodeca"]},"summary":"Attackers can cause excessive CPU consumption via crafted YAML merge keys, leading to denial of service in applications using the js-yaml library.","url":"https://insights.sbomify.com/CVE-2026-59868/"}