CVE-2025-27209

The V8 release used in Node.js v24.0.0 has changed how string hashes are computed using rapidhash. This implementation re-introduces the HashDoS vulnerability as an attacker who can control the strings to be hashed can generate many hash collisions - an attacker can generate collisions even without knowing the hash-seed. * This vulnerability affects Node.js v24.x users.

Published: 2025-07-18 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-27209 is rated Low Risk (35.4/100): CVSS High severity, with low exploitation likelihood (EPSS 0.05%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-27209

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-05-04 0.03% 0.05% +0.02%
2 2025-11-21 0.12% 0.03% -0.09%
3 2025-11-18 — 0.12% —

Full EPSS history (4 records total)

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

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-27209

OS Trackers for CVE-2025-27209

vendor priority summary link
debian unimportant CVE-2025-27209 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-27209
redhat medium — https://access.redhat.com/security/cve/CVE-2025-27209
suse medium CVE-2025-27209 severity moderate: SUSE including 34 source package names (corepack20, corepack22, …), 173 product×package rows across 22 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (22 product lines)): Known Not Affected 173. https://www.suse.com/security/cve/CVE-2025-27209/
ubuntu medium CVE-2025-27209 medium priority: Ubuntu including 1 source packages (nodejs), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, trusty, upstream, xenial): not-affected 8. https://ubuntu.com/security/CVE-2025-27209

Affected software / configurations for CVE-2025-27209

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-27209

cvelogic Threat Intelligence