npm vulnerability intelligence

js-yaml NPM Package
Vulnerability Check

YAML 1.2 parser and serializer

Critical MIT v4.1.1
Vulnerability Analysis OSV Live

js-yaml

v4.1.1 · MIT · 232,673,598 dl/wk

Advisory Breakdown

Critical 1
High 1
Moderate 2
Low 0

Severity Rating

Critical

4 advisories

Critical

Weekly downloads

232,673,598

Total advisories

4

Latest version

4.1.1

License

MIT

Advisories Package Info Runtime

Known advisories

OSV records for the npm ecosystem

4
GHSA-2pr6-76vf-7546 moderate

Denial of Service in js-yaml

Affected: >=0 <3.13.0 Fixed in: 3.13.0 Updated Aug 4, 2021
View source
GHSA-8j8c-7jfh-h6hx high

Code Injection in js-yaml

Affected: >=0 <3.13.1 Fixed in: 3.13.1 Updated Aug 31, 2020
View source
GHSA-mh29-5h37-fv8m CVE-2025-64718 moderate

js-yaml has prototype pollution in merge (<<)

Affected: >=4.0.0 <4.1.1, >=0 <3.14.2 Fixed in: 4.1.1, 3.14.2 Updated Feb 4, 2026
View source
GHSA-xxvw-45rp-3mj2 CVE-2013-4660 critical

Deserialization Code Execution in js-yaml

Affected: >=0 <2.0.5 Fixed in: 2.0.5 Updated Nov 8, 2023
View source

Checked May 22, 2026, 7:06 PM from npm and OSV.dev

Package metadata

From the npm registry

Package name
js-yaml
Ecosystem
npm
Latest version
4.1.1
License
MIT
Weekly downloads
232,673,598
Repository
Open repository

Remediation boundary

What RequestGuard does — and doesn't — cover

RequestGuard does not fix npm package vulnerabilities. Dependency remediation happens through package updates, patches, lockfile changes, and maintainer guidance. RequestGuard can help mitigate runtime abuse around exposed web and API flows while remediation is handled separately.

Signup flows
Login attempts
API traffic

Protect runtime flows →

Allow, challenge, review, and block decisions for exposed endpoints.

Data from npm registry and OSV.dev · Checked 5/22/2026, 7:06:04 PM