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

CVE-2022-25883 — semver

MEDIUMFix: npm/node-semver@717534e

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

semver vulnerable to Regular Expression Denial of Service

Also known asGHSA-c2qf-rxjj-qqgw
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-25883.

EPSS Exploitation Probability

via FIRST.org ↗
2.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk
0.00%1.14%2.27%3.41%0.6%2.8%May 26Sep 26Nov 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

3 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.

40Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
semvernpm
1135.4Mdownloads / week

Description

Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.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
📦npmsemver≥ 7.0.0&&< 7.5.27.5.2npm install semver@7.5.2
📦npmsemver≥ 6.0.0&&< 6.3.16.3.1npm install semver@6.3.1
📦npmsemver≥ 2.0.0-alpha&&< 5.7.25.7.2npm install semver@5.7.2

Affected Products

1 product · 3 configurations
Application
semvernpmjs
≥ 7.0.0 && < 7.5.3
range
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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  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

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability is rated Moderate for Red Hat Products versus NVD's High due to deployment context. The flaw in node-semver's new Range() function causes catastrophic regex backtracking on crafted input, leading to CPU exhaustion. However, exploitation requires untrusted input passed directly to the parser. So…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Source: Red Hat security advisory for CVE-2022-25883 (CC BY 4.0)
ProductFixed inAdvisory
Migration Toolkit for Runtimes 1 on RHEL 8mtr/mtr-web-container-rhel8:1.2-10RHSA-2024:0719
multicluster engine for Kubernetes 2.6 for RHEL 8multicluster-engine/assisted-image-service-rhel8:v2.6.2-5RHSA-2024:5955
NETWORK-OBSERVABILITY-1.4.0-RHEL-9network-observability/network-observability-console-plugin-rhel9:v1.4.0-42RHSA-2023:5379
Red Hat Advanced Cluster Management for Kubernetes 2.11 for RHEL 9rhacm2/acm-cluster-permission-rhel9:v2.11.2-5RHSA-2024:6044
Red Hat Enterprise Linux 8nodejs:16-8080020230906092006.63b34585RHSA-2023:5360
Red Hat Enterprise Linux 8nodejs:18-8080020230825111344.63b34585RHSA-2023:5362
Red Hat Enterprise Linux 8.6 Extended Update Supportnodejs:16-8060020230906023909.ad008a3aRHSA-2023:5361
Red Hat Enterprise Linux 9nodejs:18-9020020230825081254.rhel9RHSA-2023:5363

Frequently Asked Questions

Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.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?

Find it across npm, including transitive dependencies.

CVE-2022-25883: semver DoS — Fixed in 7.5.2