CVE-2025-55130VulnerabilityPublished 20 Jan 2026Updated 27 Oct 2026

Nodejs: A flaw

Affects nodejsSource GCVE Database

Authoritative record:CVE-2025-55130· High 7.1

Not known to be exploited · CVSS 7.1 High.

Data as of 27 Oct 2026, 06:42 UTC

CVSS 3.0 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSnodejs`pkg:deb/ubuntu/nodejs?arch=source&distro=resolute`Other threats	Affected 20.19.4+dfsg-1 – 22.22.1+dfsg+~cs22.19.15-1ubuntu1 6 affected builds	Fixed in–
Ubuntu 25.10nodejs`pkg:deb/ubuntu/nodejs?arch=source&distro=questing`Other threats	Affected =20.18.1+dfsg-1ubuntu2 =20.19.2+dfsg-1 =20.19.4+dfsg-1	Fixed in–
Ubuntu 24.04 LTSnodejs`pkg:deb/ubuntu/nodejs?arch=source&distro=noble`Other threats	Affected 18.13.0+dfsg1-1ubuntu2 – 18.19.1+dfsg-6ubuntu5 5 affected builds	Fixed in–
Ubuntu Pro 22.04 LTSnodejs`pkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/jammy`Other threats	Affected 12.22.5~dfsg-5ubuntu1 – 12.22.9~dfsg-1ubuntu3.6+esm2 12 affected builds	Fixed in–
Ubuntu Pro 20.04 LTSnodejs`pkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/focal`Other threats	Affected 10.15.2~dfsg-2ubuntu1 – 10.19.0~dfsg-3ubuntu1.6+esm2 10 affected builds	Fixed in–
Ubuntu Pro 18.04 LTSnodejs`pkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/bionic`Other threats	Affected 6.11.4~dfsg-1ubuntu1 – 8.10.0~dfsg-2ubuntu0.4+esm6 15 affected builds	Fixed in–

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

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…