Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-55130: Vulnerability in nodejs node

0
High
VulnerabilityCVE-2025-55130cvecve-2025-55130
Published: Tue Jan 20 2026 (01/20/2026, 20:41:55 UTC)
Source: CVE Database V5
Vendor/Project: nodejs
Product: node

Description

CVE-2025-55130 is a high-severity vulnerability in Node. js versions 20. 19. 6, 22. 21. 1, 24. 12. 0, and 25. 2. 1 that allows attackers to bypass the file system permission restrictions (--allow-fs-read and --allow-fs-write) by exploiting crafted relative symlink paths.

AI-Powered Analysis

AILast updated: 01/20/2026, 21:06:25 UTC

Technical Analysis

CVE-2025-55130 is a vulnerability in the Node.js runtime's permission model that allows attackers to bypass the --allow-fs-read and --allow-fs-write restrictions. Node.js introduced a permission model to restrict file system access for scripts, typically limiting read and write operations to specific directories. However, this vulnerability arises because the permission checks do not correctly handle crafted relative symbolic link (symlink) paths. By chaining multiple directories and symlinks, an attacker can escape the intended sandbox directory and access files outside the allowed scope. This flaw breaks the isolation guarantees expected from the permission model, enabling arbitrary file read and write operations. The vulnerability affects Node.js versions 20.19.6, 22.21.1, 24.12.0, and 25.2.1. The attack complexity is low, requiring only local privileges and no user interaction, but it does require the attacker to have some level of code execution within the Node.js environment with restricted permissions. The impact includes high confidentiality and integrity loss, as sensitive files can be read or modified, potentially leading to system compromise or data leakage. No patches or known exploits are currently documented, but the vulnerability is publicly disclosed and assigned a CVSS v3.0 score of 7.1, indicating high severity. The flaw is particularly critical for environments running untrusted or semi-trusted code with Node.js permission restrictions enabled, such as multi-tenant cloud platforms, development environments, or containerized applications.

Potential Impact

For European organizations, this vulnerability poses a significant risk to confidentiality and integrity of sensitive data and systems. Organizations relying on Node.js for backend services, especially those using the permission model to sandbox scripts, could see unauthorized access to critical files, including configuration files, credentials, or proprietary data. This could lead to data breaches, unauthorized data modification, or further system compromise. The vulnerability is particularly concerning for cloud service providers, software development companies, and enterprises using Node.js in multi-tenant or containerized environments common in Europe. The ability to bypass file system restrictions undermines trust in Node.js sandboxing, potentially exposing regulated data subject to GDPR and other compliance requirements. Although exploitation requires local privileges, the ease of bypassing restrictions means that any compromised or malicious code running under Node.js could escalate its access, increasing the attack surface. This could also facilitate lateral movement within networks, impacting operational continuity and data security.

Mitigation Recommendations

1. Monitor Node.js official channels for patches addressing CVE-2025-55130 and apply updates promptly once available. 2. Until patches are released, avoid running untrusted or semi-trusted code with Node.js permission model restrictions enabled. 3. Implement strict code review and validation processes to prevent malicious or vulnerable scripts from executing in Node.js environments. 4. Restrict the use of symbolic links in directories accessible to Node.js scripts, or audit symlink usage to detect suspicious chaining. 5. Employ runtime monitoring and file integrity checking to detect unauthorized file access or modifications. 6. Use containerization or sandboxing at the OS level to add an additional layer of isolation beyond Node.js permissions. 7. Limit local user privileges to reduce the risk of local code execution that could exploit this vulnerability. 8. Educate developers and system administrators about the risks of symlink traversal and the importance of secure permission configurations in Node.js.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
hackerone
Date Reserved
2025-08-07T15:00:05.576Z
Cvss Version
3.0
State
PUBLISHED

Threat ID: 696feab04623b1157c4e3b6c

Added to database: 1/20/2026, 8:50:56 PM

Last enriched: 1/20/2026, 9:06:25 PM

Last updated: 1/20/2026, 11:30:44 PM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Related Threats

CVE-2026-0933: CWE-20 Improper Input Validation in Cloudflare Wrangler

High
VulnerabilityTue Jan 20 2026

CVE-2026-0672: CWE-93 in Python Software Foundation CPython

Medium
VulnerabilityTue Jan 20 2026

CVE-2026-21990: Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. in Oracle Corporation Oracle VM VirtualBox

High
VulnerabilityTue Jan 20 2026

CVE-2026-21989: Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. in Oracle Corporation Oracle VM VirtualBox

High
VulnerabilityTue Jan 20 2026

CVE-2026-21988: Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. in Oracle Corporation Oracle VM VirtualBox

High
VulnerabilityTue Jan 20 2026

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats