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-25762: CWE-400: Uncontrolled Resource Consumption in adonisjs core

0
High
VulnerabilityCVE-2026-25762cvecve-2026-25762cwe-400cwe-770
Published: Fri Feb 06 2026 (02/06/2026, 22:48:55 UTC)
Source: CVE Database V5
Vendor/Project: adonisjs
Product: core

Description

AdonisJS is a TypeScript-first web framework. Prior to versions 10.1.3 and 11.0.0-next.9, a denial of service (DoS) vulnerability exists in the multipart file handling logic of @adonisjs/bodyparser. When processing file uploads, the multipart parser may accumulate an unbounded amount of data in memory while attempting to detect file types, potentially leading to excessive memory consumption and process termination. This issue has been patched in versions 10.1.3 and 11.0.0-next.9.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/14/2026, 12:13:15 UTC

Technical Analysis

CVE-2026-25762 is a denial of service (DoS) vulnerability identified in the core of AdonisJS, a TypeScript-first web framework widely used for building server-side applications. The vulnerability specifically resides in the multipart file handling logic of the @adonisjs/bodyparser package, which is responsible for parsing multipart/form-data requests, commonly used for file uploads. In versions prior to 10.1.3 and 11.0.0-next.9, the multipart parser attempts to detect file types by accumulating data in memory without proper bounds checking. This uncontrolled resource consumption (CWE-400) can lead to excessive memory usage, causing the Node.js process to terminate unexpectedly due to out-of-memory conditions. The vulnerability does not require any authentication or user interaction, making it remotely exploitable by sending specially crafted multipart requests with large or numerous file uploads. The impact is limited to availability (denial of service), with no direct confidentiality or integrity compromise. The issue has been addressed in the patched versions 10.1.3 and 11.0.0-next.9 by implementing proper memory usage limits during file type detection. No known exploits have been reported in the wild as of the publication date, but the vulnerability poses a significant risk to applications relying on vulnerable versions of AdonisJS, especially those exposed to untrusted users or the internet. The CVSS v3.1 base score is 7.5, reflecting high severity due to network vector, low attack complexity, no privileges required, and no user interaction needed.

Potential Impact

For European organizations, this vulnerability can lead to denial of service conditions in web applications built on vulnerable versions of AdonisJS. This can result in service outages, degraded user experience, and potential loss of business continuity, especially for public-facing applications handling file uploads. Organizations in sectors such as e-commerce, government services, and online platforms that rely on Node.js frameworks may face operational disruptions. The vulnerability could be exploited by attackers to cause repeated crashes or resource exhaustion, potentially leading to downtime during critical business hours. Although it does not compromise data confidentiality or integrity, the availability impact alone can have significant reputational and financial consequences. Additionally, remediation efforts during an active attack could divert IT resources and increase incident response costs.

Mitigation Recommendations

European organizations should immediately upgrade any AdonisJS installations using @adonisjs/bodyparser to version 10.1.3 or later, or 11.0.0-next.9 or later, where the vulnerability is patched. Beyond upgrading, organizations should implement strict resource limits on file upload sizes and request rates at the web server or application firewall level to prevent abuse. Employing rate limiting and anomaly detection on multipart/form-data requests can help identify and block suspicious traffic patterns. Additionally, isolating file upload handling processes and monitoring memory usage metrics can provide early warning of exploitation attempts. Security teams should review application logs for unusual multipart upload activity and prepare incident response plans for potential DoS events. Regular dependency audits and timely patch management are critical to prevent exploitation of similar vulnerabilities.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-05T18:35:52.358Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69867278f9fa50a62f39d4ff

Added to database: 2/6/2026, 11:00:08 PM

Last enriched: 2/14/2026, 12:13:15 PM

Last updated: 3/22/2026, 8:26:13 PM

Views: 65

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses