NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2021-3795 — semver-regex

HIGHFix: sindresorhus/semver-regex@11c6624

CVE-2021-3795 is a high-severity (CVSS 7.5) CWE-1333 vulnerability in semver-regex. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for semver-regex — see the affected versions and patch details below.

semver-regex Regular Expression Denial of Service (ReDOS)

Also known asGHSA-44c6-4v22-4mhx
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk
0.00%0.67%1.34%2.02%0.2%1.5%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

245other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
semver-regexnpm
8.8Mdownloads / week

Description

npm semver-regex is vulnerable to Inefficient Regular Expression Complexity

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmsemver-regexall versions3.1.3npm install semver-regex@3.1.3
📦npmsemver-regex≥ 4.0.0&&< 4.0.14.0.1npm install semver-regex@4.0.1

Affected Products

1 product · 2 configurations
Application
semver-regexsemver-regex_project
< 3.1.3
1 version
4.0.0
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for semver-regex, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update semver-regex to 3.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-3795 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

npm `semver-regex` is vulnerable to Inefficient Regular Expression Complexity
O3 Security · Impact-Aware SCA

Is CVE-2021-3795 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2021-3795: semver-regex — Fixed in 3.1.3