CVE-2026-25762
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAdonisJS 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA denial of service vulnerability exists in @adonisjs/bodyparser's multipart file handling. When processing file uploads, the parser accumulates unbounded data in memory while attempting to detect file types, causing excessive memory consumption that can crash the process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.1.3>= 10.1.4, < 11.0.0= 11.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed @adonisjs/bodyparser versionRun `npm list @adonisjs/bodyparser` or inspect package.json dependencies to identify the installed versionAffected if The installed version is less than 10.1.3, or between 10.1.4 and 11.0.0 (inclusive), or exactly 11.0.0
-
Verify multipart file upload usageSearch your codebase for multipart form handling - look for route handlers using request.file() or request.files(), or check if your routes accept multipart/form-data content typesAffected if Your application processes multipart form data file uploads
-
Inspect bodyparser configurationReview your bodyparser configuration file (typically config/bodyparser.ts) for multipart and file parsing settings, particularly the 'files' property configurationAffected if Multipart file parsing is enabled in the bodyparser configuration
You are affected if you have a vulnerable @adonisjs/bodyparser version AND your application processes multipart file uploads
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.1.311.0.0
Upgrade @adonisjs/bodyparser to version 10.1.3, 11.0.0-next.9, or later to patch the vulnerability.
Upgrade to @adonisjs/bodyparser version 10.1.3 (for 10.x line) or 11.0.0-next.9 (for 11.x line)
- 1. Identify the current @adonisjs/bodyparser version in your project by reviewing package.json
- 2. If running version 10.x (< 10.1.3), upgrade to version 10.1.3 or later using: npm install @adonisjs/bodyparser@^10.1.3 or yarn add @adonisjs/bodyparser@^10.1.3
- 3. If running version 11.x (= 11.0.0), upgrade to version 11.0.0-next.9 or later (or wait for stable 11.x release with patch)
- 4. After upgrading, test multipart file upload functionality to ensure the application works correctly
- 5. Verify the fix is applied by checking the installed version: npm list @adonisjs/bodyparser
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25762 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25762 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data