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-2026-21440: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in adonisjs core

0
Critical
VulnerabilityCVE-2026-21440cvecve-2026-21440cwe-22
Published: Fri Jan 02 2026 (01/02/2026, 19:02:18 UTC)
Source: CVE Database V5
Vendor/Project: adonisjs
Product: core

Description

AdonisJS is a TypeScript-first web framework. A Path Traversal vulnerability in AdonisJS multipart file handling may allow a remote attacker to write arbitrary files to arbitrary locations on the server filesystem. This impacts @adonisjs/bodyparser through version 10.1.1 and 11.x prerelease versions prior to 11.0.0-next.6. This issue has been patched in @adonisjs/bodyparser versions 10.1.2 and 11.0.0-next.6.

AI-Powered Analysis

AILast updated: 01/09/2026, 21:20:49 UTC

Technical Analysis

CVE-2026-21440 is a path traversal vulnerability classified under CWE-22, found in the multipart file handling mechanism of the AdonisJS web framework, specifically in the @adonisjs/bodyparser package. AdonisJS is a popular TypeScript-first Node.js framework used for building web applications. The vulnerability allows a remote attacker to craft multipart file upload requests that bypass directory restrictions, enabling arbitrary file writes to any location on the server filesystem. This can lead to overwriting critical system files, uploading web shells, or injecting malicious code, potentially resulting in full server compromise. The flaw affects all @adonisjs/bodyparser versions before 10.1.2 and prerelease 11.x versions prior to 11.0.0-next.6. The vulnerability requires no authentication or user interaction, making it highly exploitable remotely over the network. The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) indicates network attack vector, low complexity, partial attack complexity, no privileges required, no user interaction, and high impact on confidentiality, integrity, and availability. Although no public exploits have been observed, the critical nature and ease of exploitation make this a significant threat to any web application using vulnerable AdonisJS versions. The issue was publicly disclosed on January 2, 2026, and patches are available in versions 10.1.2 and 11.0.0-next.6. Organizations relying on AdonisJS should prioritize updating and review multipart file upload handling to prevent exploitation.

Potential Impact

For European organizations, this vulnerability poses a severe risk to web applications built on AdonisJS, especially those handling sensitive data or critical services. Successful exploitation can lead to arbitrary file writes, enabling attackers to deploy web shells, manipulate application logic, exfiltrate data, or disrupt services. This can result in data breaches, loss of service availability, reputational damage, and regulatory non-compliance under GDPR. Given the widespread use of Node.js and TypeScript in European tech sectors, including fintech, e-commerce, and public services, the impact could be broad. Attackers could leverage this vulnerability to pivot within networks, escalate privileges, or conduct ransomware attacks. The lack of required authentication and user interaction increases the risk of automated exploitation campaigns targeting vulnerable servers. Organizations with exposed web servers or APIs using vulnerable AdonisJS versions are particularly at risk.

Mitigation Recommendations

1. Immediately upgrade @adonisjs/bodyparser to version 10.1.2 or later, or 11.0.0-next.6 or later for prerelease users. 2. Implement strict validation and sanitization of file upload paths to ensure no directory traversal sequences (e.g., '../') are accepted. 3. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with rules to detect and block suspicious multipart requests attempting path traversal. 4. Restrict file system permissions for the application process to the minimum necessary directories to limit damage from arbitrary writes. 5. Conduct thorough code reviews and penetration testing focused on file upload functionality. 6. Monitor logs for unusual file write activities or access to sensitive paths. 7. Educate developers on secure file handling practices and keep dependencies up to date. 8. Consider containerization or sandboxing to isolate the application environment and reduce attack surface.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-29T03:00:29.276Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69581901db813ff03efbfead

Added to database: 1/2/2026, 7:14:09 PM

Last enriched: 1/9/2026, 9:20:49 PM

Last updated: 2/7/2026, 3:21:02 AM

Views: 702

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.

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