CVE-2025-23166

The C++ method SignTraits::DeriveBits() may incorrectly call ThrowException() based on user-supplied inputs when executing in a background thread, crashing the Node.js process. Such cryptographic operations are commonly applied to untrusted inputs. Thus, this mechanism potentially allows an adversary to remotely crash a Node.js runtime.

Published: 2025-05-19 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-23166 is rated Moderate Risk (48.9/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.30%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-23166

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-15 0.10% 0.30% +0.21%
2 2026-03-04 0.04% 0.10% +0.05%
3 2026-03-01 — 0.04% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-23166

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-23166

OS Trackers for CVE-2025-23166

vendor priority summary link
alpine high CVE-2025-23166: 1 source package rows (nodejs); 2 state rows across 2 repos (3.21-main, edge-main); fixed 2, open 0. https://security.alpinelinux.org/vuln/CVE-2025-23166
debian unimportant CVE-2025-23166 unimportant priority: Debian including 1 source packages (nodejs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-23166
redhat high — https://access.redhat.com/security/cve/CVE-2025-23166
suse high CVE-2025-23166 severity important: SUSE including 74 source package names (0.0.17-1.1:nodejs22-22.15.1-150600.13.9.1, 0.0.17-1.1:npm22-22.15.1-150600.13.9.1, …), 138 product×package rows across 21 product lines (Container bci/nodejs, Container containers/open-webui, … (21 product lines)): Fixed 78, Known Not Affected 60. https://www.suse.com/security/cve/CVE-2025-23166/
ubuntu medium CVE-2025-23166 medium priority: Ubuntu including 1 source packages (nodejs), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 6, ignored 2, needed 1, released 1. https://ubuntu.com/security/CVE-2025-23166

Affected software / configurations for CVE-2025-23166

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-23166

cvelogic Threat Intelligence