VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

semver: vulnerability history, versions and safety

semver is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 72 releases, from Oct 2017 to Jun 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all semver vulnerabilities

Vulert verdict on semver 7.8.5 i

Updated on 22 Oct 2026

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

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

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

  • Current release 7.8.5 — unaffected i
  • Vulnerabilities on record 2 over 5 years · 0 in the last year i
  • Latest disclosure 21 Jun 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 434,841 packages i
  • Stars 5,466 i
  • OpenSSF scorecard 4/10 i
  • Last release 4 months ago i
  • Licence ISC i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 semver, 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
7.8.5 19 Jun 2026 none ISC — Details →
7.8.4 09 Jun 2026 none ISC — Details →
7.8.3 08 Jun 2026 none ISC — Details →
7.8.2 04 Jun 2026 none ISC — Details →
7.8.1 21 May 2026 none ISC — Details →
7.8.0 08 May 2026 none ISC — Details →
7.7.4 05 Feb 2026 none ISC — Details →
7.7.3 07 Oct 2025 none ISC — Details →
7.7.2 12 May 2025 none ISC — Details →
7.7.1 03 Feb 2025 none ISC — Details →
7.7.0 29 Jan 2025 none ISC — Details →
7.6.3 16 Jul 2024 none ISC — Details →
7.6.2 09 May 2024 none ISC — Details →
7.6.1 07 May 2024 none ISC — Details →
7.6.0 05 Feb 2024 none ISC — Details →
6.3.1 10 Jul 2023 none ISC — Details →
5.7.2 10 Jul 2023 none ISC — Details →
7.5.4 07 Jul 2023 none ISC — Details →
7.5.3 22 Jun 2023 none ISC — Details →
7.5.2 15 Jun 2023 none ISC — Details →
7.5.1 12 May 2023 H1 ISC Yes Details →
7.5.0 17 Apr 2023 H1 ISC Yes Details →
7.4.0 10 Apr 2023 H1 ISC Yes Details →
7.3.8 04 Oct 2022 H1 ISC Yes Details →
7.3.7 12 Apr 2022 H1 ISC Yes Details →
7.3.6 06 Apr 2022 H1 ISC Yes Details →
7.3.5 23 Mar 2021 H1 ISC Yes Details →
7.3.4 01 Dec 2020 H1 ISC Yes Details →
7.3.3 01 Dec 2020 H1 ISC Yes Details →
7.3.2 14 Apr 2020 H1 ISC Yes Details →
7.3.1 14 Apr 2020 H1 ISC Yes Details →
7.3.0 14 Apr 2020 H1 ISC Yes Details →
7.2.3 13 Apr 2020 H1 ISC Yes Details →
7.2.2 10 Apr 2020 H1 ISC Yes Details →
7.2.1 06 Apr 2020 H1 ISC Yes Details →
7.2.0 06 Apr 2020 H1 ISC Yes Details →
7.1.3 11 Feb 2020 H1 ISC Yes Details →
7.1.2 31 Jan 2020 H1 ISC Yes Details →
7.1.1 17 Dec 2019 H1 ISC Yes Details →
7.1.0 17 Dec 2019 H1 ISC Yes Details →
7.0.0 14 Dec 2019 H1 ISC Yes Details →
5.7.1 12 Aug 2019 none ISC — Details →
6.3.0 23 Jul 2019 none ISC — Details →
6.2.0 01 Jul 2019 none ISC — Details →
6.1.3 01 Jul 2019 none ISC — Details →
6.1.2 24 Jun 2019 none ISC — Details →
6.1.1 28 May 2019 none ISC — Details →
6.1.0 22 May 2019 none ISC — Details →
6.0.0 26 Mar 2019 none ISC — Details →
5.7.0 26 Mar 2019 none ISC — Details →
5.6.0 10 Oct 2018 none ISC — Details →
5.5.1 17 Aug 2018 none ISC — Details →
5.5.0 16 Jan 2018 none ISC — Details →
5.4.1 24 Jul 2017 none ISC — Details →
5.4.0 24 Jul 2017 none ISC — Details →
5.3.0 14 Jul 2016 none ISC — Details →
5.2.0 28 Jun 2016 none ISC — Details →
5.1.1 23 Jun 2016 none ISC — Details →
5.1.0 18 Nov 2015 none ISC — Details →
5.0.3 11 Sep 2015 none ISC — Details →
5.0.2 11 Sep 2015 none ISC — Details →
5.0.1 13 Jul 2015 none ISC — Details →
5.0.0 11 Jul 2015 none ISC — Details →
4.3.6 01 Jun 2015 none ISC — Details →
4.3.5 29 May 2015 none ISC — Details →
4.3.4 05 May 2015 none ISC — Details →
4.3.3 27 Mar 2015 none non-standard — Details →
4.3.2 27 Mar 2015 none non-standard — Details →
4.3.1 24 Feb 2015 H1 non-standard Yes Details →
4.3.0 12 Feb 2015 H1 non-standard Yes Details →
4.2.2 10 Feb 2015 H1 non-standard Yes Details →
4.2.1 10 Feb 2015 H1 non-standard Yes Details →
4.2.0 23 Dec 2014 H1 non-standard Yes Details →
4.1.1 19 Dec 2014 H1 non-standard Yes Details →
4.1.0 16 Oct 2014 H1 non-standard Yes Details →
4.0.3 01 Oct 2014 H1 non-standard Yes Details →
4.0.2 30 Sep 2014 H1 non-standard Yes Details →
4.0.0 11 Sep 2014 H1 non-standard Yes Details →
3.0.1 24 Jul 2014 H1 non-standard Yes Details →
3.0.0 23 Jul 2014 H1 non-standard Yes Details →
2.3.2 22 Jul 2014 H1 non-standard Yes Details →
2.3.1 18 Jun 2014 H1 non-standard Yes Details →
2.3.0 07 May 2014 H1 non-standard Yes Details →
2.2.1 28 Oct 2013 H1 non-standard Yes Details →
2.2.0 25 Oct 2013 H1 non-standard Yes Details →
2.1.0 01 Aug 2013 H1 non-standard Yes Details →
2.0.11 24 Jul 2013 H1 non-standard Yes Details →
2.0.10 09 Jul 2013 H1 non-standard Yes Details →
2.0.9 06 Jul 2013 H1 non-standard Yes Details →
2.0.8 24 Jun 2013 H1 non-standard Yes Details →
2.0.7 20 Jun 2013 H1 non-standard Yes Details →
2.0.6 20 Jun 2013 H1 non-standard Yes Details →
2.0.5 20 Jun 2013 H1 non-standard Yes Details →
2.0.4 20 Jun 2013 H1 non-standard Yes Details →
2.0.3 20 Jun 2013 H1 non-standard Yes Details →
2.0.2 20 Jun 2013 H1 non-standard Yes Details →
2.0.1 20 Jun 2013 H1 non-standard Yes Details →
2.0.0-beta 18 Jun 2013 H1 non-standard Yes Details →
2.0.0-alpha 15 Jun 2013 H1 non-standard Yes Details →
1.1.4 01 Mar 2013 H1 MIT Yes Details →
1.1.3 06 Feb 2013 H1 — Yes Details →
1.1.2 06 Jan 2013 H1 — Yes Details →
1.1.1 29 Nov 2012 H1 — Yes Details →
1.1.0 02 Oct 2012 H1 — Yes Details →
1.0.14 27 May 2012 H1 — Yes Details →
1.0.13 21 Dec 2011 H1 — Yes Details →
1.0.12 18 Nov 2011 H1 — Yes Details →
1.0.11 15 Nov 2011 H1 — Yes Details →
1.0.10 04 Oct 2011 H1 — Yes Details →
1.0.9 20 Jul 2011 H1 — Yes Details →
1.0.8 27 Jun 2011 H1 — Yes Details →
1.0.7 17 Jun 2011 H1 — Yes Details →
1.0.6 21 May 2011 H1 — Yes Details →
1.0.5 03 May 2011 H1 — Yes Details →
1.0.4 21 Apr 2011 H1 — Yes Details →
1.0.3 19 Apr 2011 H1 — Yes Details →
1.0.2 22 Mar 2011 H1 — Yes Details →
1.0.1 18 Feb 2011 H1 — Yes Details →
1.0.0 12 Feb 2011 H1 — Yes Details →

All 119 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
  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for semver

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-8855: Regular Expression Denial of Service in semver 7.5 high 4.3.2 24 Oct 2017
CVE-2022-25883: semver Regular Expression Denial of Service 7.5 high 7.5.2 21 Jun 2023

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 semver

Is semver safe to use?

Vulert records 2 vulnerabilities for semver in npm: 0 critical, 2 high, 0 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 semver's Vulert package health score?

Vulert scores semver 82/100, which reads as in good shape. 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 semver affected?

No. 7.8.5, 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.

Which version of semver should I use?

7.8.5 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does semver have?

2 vulnerabilities are recorded for semver in the npm ecosystem: 0 critical, 2 high, 0 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 semver vulnerabilities disclosed?

0 vulnerabilities were recorded for semver 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 semver 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 semver for upcoming vulnerabilities?

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