# CVE-2026-25762: AdonisJS vulnerable to Denial of Service (DoS) via Unrestricted Memory Buffering in PartHandler during File Type Detection

> Attackers can cause denial of service in AdonisJS applications by uploading files that trigger unbounded memory buffering during type detection.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2026
- **Updated:** 9 Feb 2026
- **Also known as:** GHSA-xx9g-fh25-4q64

## What is CVE-2026-25762?

CVE-2026-25762 is a high-severity denial of service vulnerability in adonisjs core, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-25762?

4 open source packages ship an affected version, including @adonisjs/bodyparser. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@adonisjs/bodyparser` | npm | All versions | 10.1.3 |
| `@adonisjs/bodyparser` | npm | All versions | 10.1.3 |
| `@adonisjs/bodyparser` | npm | From 11.0.0-next.0 | 11.0.0-next.9 |
| `@adonisjs/bodyparser` | npm | From 11.0.0-next.0 | 11.0.0-next.9 |

Products: Adonisjs Bodyparser.

## How do I fix CVE-2026-25762?

Upgrade @adonisjs/bodyparser to a fixed version for your release line: 10.1.3 or 11.0.0-next.9.

## Is CVE-2026-25762 being exploited?

There is no known exploitation of CVE-2026-25762 in the wild and no public exploit code.

## Other vulnerabilities in adonisjs core

- [CVE-2026-25754](https://insights.sbomify.com/CVE-2026-25754/): AdonisJS multipart body parsing has Prototype Pollution issue (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25762 and fix it if it is affected.

What it is: CVE-2026-25762 is a high-severity denial of service vulnerability in adonisjs core, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25762 in the wild and no public exploit code.

Affected packages and fixed versions:
- @adonisjs/bodyparser (npm): affected all versions; fixed in 10.1.3
- @adonisjs/bodyparser (npm): affected all versions; fixed in 10.1.3
- @adonisjs/bodyparser (npm): affected from 11.0.0-next.0; fixed in 11.0.0-next.9
- @adonisjs/bodyparser (npm): affected from 11.0.0-next.0; fixed in 11.0.0-next.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25762/ (Markdown: https://insights.sbomify.com/CVE-2026-25762/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25762
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25762
- OSV: https://osv.dev/vulnerability/CVE-2026-25762

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25762/
Summaries are generated and may contain mistakes; the official description above is the record.