StackPrism

npm package

semver 6.3.0 vulnerability, and the version that fixes it

semver 6.3.0 has 1 known vulnerability (1 rated high or critical); 6.3.1 fixes it.

npm (opens in a new tab) describes it as “The semantic version parser used by npm.”

Known vulnerabilities
1
1 rated high or critical
Released
Jul 23, 2019
Latest is 7.8.5
Downloads last week
16.6M
2% of semver downloads
Licence
ISC
OpenSSF Scorecard
6.4/10
npm/node-semver (opens in a new tab)
Dependencies
None
Resolved by deps.dev

What to upgrade to

6.3.1 is the closest release with no known vulnerabilities.

  • 6.3.1Upgrade to this

    Fixes the known vulnerability and the newest 6.x release. Released Jul 10, 2023.

    No known vulnerabilities

  • 7.8.5

    Latest release. Released Jun 19, 2026.

    No known vulnerabilities

Hand the fix to your coding agent

One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.

Findings

Every advisory for semver 6.3.0

Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.

  1. CriticalCVE-2022-25883 on OSV.dev (opens in a new tab)GHSA-c2qf-rxjj-qqgwEPSS: top 14%

    semver vulnerable to Regular Expression Denial of Service

    Fixed in 6.3.1. Published Jun 21, 2023.

Who is still on a vulnerable semver

6% of last week’s 873.2M semver downloads went to versions with known vulnerabilities.

From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.

Is semver the only one?

Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.

Check your whole repo

How this page is checked

StackPrism asks OSV.dev which advisories affect exactly semver 6.3.0, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.

Last checked against npm, OSV.dev, deps.dev, CISA KEV and FIRST EPSS.