Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

CVE-2021-3795

HIGH

semver-regex Regular Expression Denial of Service (ReDOS)

Also known asGHSA-44c6-4v22-4mhx
Published
Sep 15, 2021
Updated
Mar 14, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk69th percentile+0.94%
0.00%0.64%1.27%1.91%0.5%1.4%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

semver-regexnpm
9.0Mdownloads / week

Description

semver-regex is vulnerable to Inefficient Regular Expression Complexity

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmsemver-regexall versions3.1.3
📦npmsemver-regex4.0.0&&< 4.0.14.0.1
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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2021-3795 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2021-3795. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

Is CVE-2021-3795 in your dependencies?

O3 detects CVE-2021-3795 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.