Is js-yaml 3.10 vulnerable?
npm · 1 release from 3.10.0 to 3.10.0 · latest js-yaml is 5.5.0 · checked 1 Nov 2026
Yes: 7 known advisories
Yes. js-yaml 3.10.0, the last 3.10 release, is affected by 7 known security advisories (4 high, 3 medium), including CVE-2026-84375, CVE-2026-59869, CVE-2026-53550. Upgrade to 3.15.2 or later to fix all of them.
npm install js-yaml@3.15.2Advisories affecting js-yaml 3.10.0
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
js-yaml: YAML merge-key chains can force quadratic CPU consumption
- Affected
- >=3.0.0 <3.15.0 · >=4.0.0 <4.3.0
- Fixed in
- 3.15.0, 4.3.0
JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases
- Affected
- >=4.0.0 <4.2.0 · <3.15.0
- Fixed in
- 3.15.0, 4.2.0
js-yaml has prototype pollution in merge (<<)
- Affected
- >=4.0.0 <4.1.1 · <3.14.2
- Fixed in
- 3.14.2, 4.1.1
Denial of Service in js-yaml
- Affected
- <3.13.0
- Fixed in
- 3.13.0
Code Injection in js-yaml
- Affected
- <3.13.1
- Fixed in
- 3.13.1
Which of your client projects are still on js-yaml 3.10?
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.