Skip to main content
VulnerabilityPublished Updated

CVE-2025-27209: Node.js · V8 release used

Affects nodeSource GCVE Database

0
Compare
Authoritative record:CVE-2025-27209· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 24.4.1 soon.

Data as of 4 Nov 2026, 18:27 UTC

CVSS 3.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (hackerone)CVSS 3.07.5
Patch
Available – fixed in 24.4.1
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade node to 24.4.1.

Affected software

ProductAffectedFixed in
Bitnaminodepkg:bitnami/nodeOther threatsAffected
  • >=24.0.0 <24.4.1
Fixed in
  • 24.4.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Node.js version 24.4.1 that fixes this vulnerability. Users should upgrade to version 24.4.1 or later to remediate the issue.

Description

A vulnerability in the V8 engine used by Node.js v24.0.0 through v24.4.0 reintroduces a HashDoS issue due to changes in string hash computation using rapidhash. This allows an attacker who controls input strings to cause many hash collisions, potentially degrading performance. The vulnerability is fixed in Node.js v24.4.1.

References

Community reviews

Loading reviews…