{"answers":{"affected":"4 open source packages ship an affected version, including js-yaml.","exploited":"There is no known exploitation of CVE-2026-84375 in the wild and no public exploit code.","fix":"Upgrade js-yaml to a fixed version for your release line: 3.15.2 or 4.3.2.","what":"CVE-2026-84375 is a high-severity denial of service vulnerability in nodeca js-yaml, published on 1 Sep 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-84375 and fix it if it is affected.\n\nWhat it is: CVE-2026-84375 is a high-severity denial of service vulnerability in nodeca js-yaml, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-84375 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- js-yaml (npm): affected from 3.0.0; fixed in 3.15.2\n- js-yaml (npm): affected from 3.0.0; fixed in 3.15.2\n- js-yaml (npm): affected from 4.0.0; fixed in 4.3.2\n- js-yaml (npm): affected from 4.0.0; fixed in 4.3.2\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-84375/ (Markdown: https://insights.sbomify.com/CVE-2026-84375/index.md)","id":"CVE-2026-84375","markdown":"https://insights.sbomify.com/CVE-2026-84375/index.md","name":"CVE-2026-84375","record":{"aliases":["CLEANSTART-2026-JR75772","CLEANSTART-2026-KE27596","CLEANSTART-2026-PJ72615","CLEANSTART-2026-PR35432","CLEANSTART-2026-TB41046","CLSA-2026-1788978094","CLSA-2026-1790183141","CLSA-2026-1790597988","CLSA-2026-1792163387","DEBIAN-CVE-2026-84375","ECHO-3185-a5dc-6763","GHSA-2883-xcg3-v3hh","MINI-2ph2-h8gq-xx95","MINI-2vcf-6rch-x89c","MINI-38hm-chr3-6pgr","MINI-4hrj-rgpm-vxhh","MINI-5g22-q72x-r2mr","MINI-64hj-gj8w-hj58","MINI-66p4-q5wv-549m","MINI-6c23-pjp5-gpch","MINI-72rj-vr4q-xrxr","MINI-7383-9322-p9ch","MINI-7697-gcxj-9p52","MINI-7v6g-pxg5-r2pv","MINI-88mv-3xgv-8w4q","MINI-89r6-5pwg-33rj","MINI-9r49-xvf5-8vfc","MINI-c3gr-557q-j83j","MINI-cvhr-q42x-7m72","MINI-cxh8-mp62-fc28","MINI-fwgm-xvx4-9qgj","MINI-g89w-gfr4-qm2v","MINI-g92w-jxx8-r759","MINI-ggxm-9238-pgr3","MINI-h4f7-vxq3-fqw6","MINI-h8h2-g259-89hg","MINI-mg87-rx9f-xr3q","MINI-mh6f-87wh-3j4p","MINI-mhx8-3vmq-89pr","MINI-pm93-w77c-jwr6","MINI-pvmh-7p86-2xrr","MINI-r82r-x23m-qqx4","MINI-vghp-7848-wh5q","MINI-w5hj-97cp-j6mx","MINI-xhxf-fp6j-xj7x","MINI-xmvq-x998-c4pm","MINI-xv66-wcvg-wp72","MINI-xx5x-hcqv-46q4","OESA-2026-4060","RHSA-2026:62810","RHSA-2026:62813","ROOT-APP-NPM-CVE-2026-84375","UBUNTU-CVE-2026-84375"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript YAML parser","requires_auth":"none","summary":"An attacker can cause excessive CPU consumption in applications parsing untrusted YAML by exploiting a flaw in merge key processing limits.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 until 3.15.2, 4.3.2, and 5.4.1, maxTotalMergeKeys in lib/js-yaml/loader.js and lib/loader.js does not count empty mapping sources while processing the merge key \u003c\u003c. An attacker can alias a large sequence of empty mappings into many merge targets, causing O(N * K) processing while totalMergeKeys remains unchanged and the configured resource limit is never reached. A relatively small YAML document can therefore cause prolonged CPU consumption in applications that parse untrusted YAML, and merge processing is enabled by default on these release lines. In v3 \u0026 v4, merge is enabled by default so the severity score is higher. This issue is fixed in versions 3.15.2, 4.3.2, and 5.4.1.","ecosystems":["Red Hat:hummingbird:1","npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources","id":"CVE-2026-84375","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":6,"n_references":8,"next":{"headline":"Astro: Authorization bypass from missing path-segment boundary check when stripping the configured base","id":"CVE-2026-84376"},"packages":[{"ecosystem":"npm","fixed":["3.15.2"],"introduced":["3.0.0"],"last_affected":[],"package":"js-yaml","purl":null,"source":"GHSA-2883-xcg3-v3hh"},{"ecosystem":"npm","fixed":["3.15.2"],"introduced":["3.0.0"],"last_affected":[],"package":"js-yaml","purl":"pkg:npm/js-yaml","source":"GHSA-2883-xcg3-v3hh"},{"ecosystem":"npm","fixed":["4.3.2"],"introduced":["4.0.0"],"last_affected":[],"package":"js-yaml","purl":null,"source":"GHSA-2883-xcg3-v3hh"},{"ecosystem":"npm","fixed":["4.3.2"],"introduced":["4.0.0"],"last_affected":[],"package":"js-yaml","purl":"pkg:npm/js-yaml","source":"GHSA-2883-xcg3-v3hh"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:12.4.9-0.5.hum1"],"introduced":["0"],"last_affected":[],"package":"grafana12.4","purl":"pkg:rpm/redhat/grafana12.4","source":"RHSA-2026:62810"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:13.2.0-0.1.4.hum1"],"introduced":["0"],"last_affected":[],"package":"grafana13.2","purl":"pkg:rpm/redhat/grafana13.2","source":"RHSA-2026:62813"}],"prev":{"headline":"Laravel Excel writes exports outside the configured filesystem disk when given a caller-controlled path","id":"CVE-2026-84374"},"products":["js-yaml"],"published":"2026-09-01","related":[],"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":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["nodeca"]},"summary":"An attacker can cause excessive CPU consumption in applications parsing untrusted YAML by exploiting a flaw in merge key processing limits.","url":"https://insights.sbomify.com/CVE-2026-84375/"}