VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

js-yaml: vulnerability history, versions and safety

js-yaml is a package in the npm ecosystem. Vulert records 13 vulnerabilities for it across 88 releases, from Oct 2017 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
13 vulnerabilities recorded C1 H6 M6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
10 in the last 12 months

Most recent disclosure 29 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all js-yaml vulnerabilities

Vulert verdict on js-yaml 5.5.0 i

Updated on 23 Oct 2026

Good news: 5.5.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 13.

Package health score 67/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 5.5.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 5.5.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 5.5.0 — unaffected i
  • Vulnerabilities on record 13 over 8 years · 10 in the last year i
  • Latest disclosure 29 Sep 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 8,080 packages i
  • Stars 6,637 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for js-yaml, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
5.5.0 15 Oct 2026 none MIT — Details →
5.4.3 05 Oct 2026 none MIT — Details →
5.4.2 13 Sep 2026 none MIT — Details →
3.15.2 26 Aug 2026 M2 MIT Yes Details →
4.3.2 26 Aug 2026 none MIT — Details →
5.4.1 26 Aug 2026 none MIT — Details →
5.4.0 25 Aug 2026 M1 MIT Yes Details →
5.3.0 14 Aug 2026 M1 MIT Yes Details →
5.2.3 01 Aug 2026 M1 MIT Yes Details →
3.15.1 31 Jul 2026 M2 MIT Yes Details →
4.3.1 31 Jul 2026 H2 MIT Yes Details →
5.2.2 23 Jul 2026 M1 MIT Yes Details →
5.2.1 02 Jul 2026 H1 M1 MIT Yes Details →
3.15.0 26 Jun 2026 M2 MIT Yes Details →
4.3.0 26 Jun 2026 H3 MIT Yes Details →
5.2.0 26 Jun 2026 H1 M2 MIT Yes Details →
5.1.0 22 Jun 2026 H1 M3 MIT Yes Details →
5.0.0 20 Jun 2026 H1 M3 MIT Yes Details →
4.2.0 31 May 2026 H3 MIT Yes Details →
3.14.2 14 Nov 2025 H1 M2 MIT Yes Details →
4.1.1 12 Nov 2025 H3 M1 MIT Yes Details →
4.1.0 14 Apr 2021 H3 M2 MIT Yes Details →
4.0.0 03 Jan 2021 H3 M2 MIT Yes Details →
3.14.1 07 Dec 2020 H1 M2 MIT Yes Details →
3.14.0 22 May 2020 H1 M2 MIT Yes Details →
3.13.1 05 Apr 2019 H1 M2 MIT Yes Details →
3.13.0 20 Mar 2019 H2 M2 MIT Yes Details →
3.12.2 26 Feb 2019 H2 M3 MIT Yes Details →
3.12.1 05 Jan 2019 H2 M3 MIT Yes Details →
3.12.0 01 Jun 2018 H2 M3 MIT Yes Details →
3.11.0 05 Mar 2018 H2 M3 MIT Yes Details →
3.10.0 11 Sep 2017 H2 M3 MIT Yes Details →
3.9.1 30 Jul 2017 H2 M3 MIT Yes Details →
3.9.0 08 Jul 2017 H2 M3 MIT Yes Details →
3.8.4 08 May 2017 H2 M3 MIT Yes Details →
3.8.3 05 Apr 2017 H2 M3 MIT Yes Details →
3.8.2 02 Mar 2017 H2 M3 MIT Yes Details →
3.8.1 07 Feb 2017 H2 M3 MIT Yes Details →
3.8.0 07 Feb 2017 H2 M3 MIT Yes Details →
3.7.0 12 Nov 2016 H2 M3 MIT Yes Details →
3.6.1 11 May 2016 H2 M3 MIT Yes Details →
3.6.0 15 Apr 2016 H2 M3 MIT Yes Details →
3.5.5 17 Mar 2016 H2 M3 MIT Yes Details →
3.5.4 09 Mar 2016 H2 M3 MIT Yes Details →
3.5.3 11 Feb 2016 H2 M3 MIT Yes Details →
3.5.2 11 Jan 2016 H2 M3 MIT Yes Details →
3.5.1 11 Jan 2016 H2 M3 MIT Yes Details →
3.5.0 10 Jan 2016 H2 M3 MIT Yes Details →
3.4.6 26 Nov 2015 H2 M3 MIT Yes Details →
3.4.5 23 Nov 2015 H2 M3 MIT Yes Details →
3.4.4 21 Nov 2015 H2 M3 MIT Yes Details →
3.4.3 10 Oct 2015 H2 M3 MIT Yes Details →
3.4.2 09 Sep 2015 H2 M3 MIT Yes Details →
3.4.1 04 Sep 2015 H2 M3 MIT Yes Details →
3.4.0 22 Aug 2015 H2 M3 MIT Yes Details →
3.3.1 13 May 2015 H2 M3 MIT Yes Details →
3.3.0 26 Apr 2015 H2 M3 MIT Yes Details →
3.2.7 19 Feb 2015 H2 M3 MIT Yes Details →
3.2.6 07 Feb 2015 H2 M3 MIT Yes Details →
3.2.5 27 Dec 2014 H2 M3 MIT Yes Details →
3.2.4 19 Dec 2014 H2 M3 MIT Yes Details →
3.2.3 08 Nov 2014 H2 M3 MIT Yes Details →
3.2.2 06 Sep 2014 H2 M3 MIT Yes Details →
3.2.1 24 Aug 2014 H2 M3 MIT Yes Details →
3.1.0 07 Jul 2014 H2 M3 MIT Yes Details →
3.0.2 27 Feb 2014 H2 M3 MIT Yes Details →
3.0.1 22 Dec 2013 H2 M3 MIT Yes Details →
3.0.0 16 Dec 2013 H2 M3 MIT Yes Details →
2.1.3 15 Oct 2013 H1 M3 MIT Yes Details →
2.1.2 06 Oct 2013 H1 M3 MIT Yes Details →
2.1.1 01 Oct 2013 H1 M3 MIT Yes Details →
2.1.0 05 Jun 2013 H1 M3 MIT Yes Details →
2.0.5 26 Apr 2013 H1 M3 MIT Yes Details →
2.0.4 08 Apr 2013 C1 H1 M3 MIT Yes Details →
2.0.3 26 Feb 2013 C1 H1 M3 MIT Yes Details →
2.0.2 15 Feb 2013 C1 H1 M3 MIT Yes Details →
2.0.1 09 Feb 2013 C1 H1 M3 MIT Yes Details →
2.0.0 09 Feb 2013 C1 H1 M3 MIT Yes Details →
1.0.3 05 Nov 2012 C1 H1 M3 MIT Yes Details →
1.0.2 02 Aug 2012 C1 H1 M3 MIT Yes Details →
1.0.1 07 Jul 2012 C1 H1 M3 MIT Yes Details →
1.0.0 01 Jul 2012 C1 H1 M3 MIT Yes Details →
0.3.7 28 Feb 2012 C1 H1 M3 MIT Yes Details →
0.3.6 22 Feb 2012 C1 H1 M3 MIT Yes Details →
0.3.5 10 Jan 2012 C1 H1 M3 MIT Yes Details →
0.3.4 24 Dec 2011 C1 H1 M3 MIT Yes Details →
0.3.3 20 Dec 2011 C1 H1 M3 MIT Yes Details →
0.3.2 16 Dec 2011 C1 H1 M3 MIT Yes Details →
0.3.1 18 Nov 2011 C1 H1 M3 MIT Yes Details →
0.3.0 09 Nov 2011 C1 H1 M3 MIT Yes Details →
0.2.2 06 Nov 2011 C1 H1 M3 MIT Yes Details →
0.2.1 02 Nov 2011 C1 H1 M3 MIT Yes Details →
0.2.0 02 Nov 2011 C1 H1 M3 MIT Yes Details →

All 93 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2019 2
  • 2025 1
  • 2026 9

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 10 of the 13 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for js-yaml

The 5 most severe of 13 vulnerabilities recorded for this package

Search all 13 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in js-yaml: Quadratic CPU Consumption in !!omap Resolution 7.5 high 4.3.1 06 Aug 2026
Denial of Service Vulnerability in js-yaml: Exponential Parsing Time 7.5 high 5.2.2 24 Jul 2026
CVE-2026-59869: js-yaml YAML Merge-Key Chains Cause Quadratic CPU Consumption 7.5 high 3.15.0 20 Jul 2026
CVE-2026-84375: js-yaml CPU Consumption Vulnerability Due to Unchecked Merge Keys 7.5 high 4.3.2 08 Sep 2026
CVE-2026-84375: js-yaml CPU Consumption Vulnerability Due to Unbounded Merge Keys 7.5 high 4.3.2 08 Sep 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About js-yaml

Is js-yaml safe to use?

Vulert records 13 vulnerabilities for js-yaml in npm: 1 critical, 6 high, 6 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is js-yaml's Vulert package health score?

Vulert scores js-yaml 67/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of js-yaml affected?

No. 5.5.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does js-yaml have?

13 vulnerabilities are recorded for js-yaml in the npm ecosystem: 1 critical, 6 high, 6 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new js-yaml vulnerabilities disclosed?

10 vulnerabilities were recorded for js-yaml in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of js-yaml are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor js-yaml for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the js-yaml version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.