Skip to main content
CVE-2025-55130VulnerabilityPublished Updated

CVE-2025-55130: nodejs node · Vulnerability

Affects nodejs nodeSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.6% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • >=20.19.6 <=20.19.6
  • >=22.21.1 <=22.21.1
  • >=24.12.0 <=24.12.0
  • >=25.2.1 <=25.2.1
Fixed in–

AI-suggested

Red Hat has published security advisories and issued updated Node.js packages that fix this vulnerability. Users of affected Node.js versions on Red Hat Enterprise Linux should apply the official security updates as detailed in Red Hat advisories (e.g., RHSA-2026:2899). Since this is not a cloud service, remediation requires updating the affected Node.js packages to the fixed versions provided by the vendor. Patch status is confirmed by Red Hat advisories. No alternative mitigations are specified beyond applying the vendor-provided updates.

Description

A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.

References

Community reviews

Loading reviews…