Is js-yaml 4.3 vulnerable?
npm · 3 releases from 4.3.0 to 4.3.2 · latest js-yaml is 5.5.0 · checked 1 Nov 2026
No known advisories in the last release
js-yaml 4.3.2, the last 4.3 release, has no known advisories. 2 advisories affect earlier 4.3.x releases, so update to 4.3.2.
Update within 4.3:
npm install js-yaml@4.3.2Fixed within 4.3.x, affecting earlier releases
js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
- Affected
- >=4.0.0 <4.3.2 · >=3.0.0 <3.15.2
- Fixed in
- 3.15.2, 4.3.2
JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported
- Affected
- >=4.0.0 <4.3.1 · >=3.0.0 <3.15.1
- Fixed in
- 3.15.1, 4.3.1
Which of your client projects are still on js-yaml 4.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact js-yaml version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other js-yaml versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.