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

CVE-2022-25883

MEDIUM

CVE-2022-25883 is a medium-severity (CVSS 5.3) CWE-1333 vulnerability in semver. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2022-25883 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

semver vulnerable to Regular Expression Denial of Service

Also known asGHSA-c2qf-rxjj-qqgw
Published
Jun 21, 2023
Updated
Jul 15, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known

Blast Radius

3 pkgs affected

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

semvernpm
835.9Mdownloads / week

Description

Versions of the package semver before 7.5.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
📦npmsemver7.0.0&&< 7.5.27.5.2
📦npmsemver6.0.0&&< 6.3.16.3.1
📦npmsemver2.0.0-alpha&&< 5.7.25.7.2
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. 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 to 7.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25883 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-2022-25883 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-2022-25883. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of the package semver before 7.5.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.
O3 Security · Impact-Aware SCA

Is CVE-2022-25883 in your dependencies?

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