# CVE-2026-48795: Incomplete fix for CVE-2026-25754 in @adonisjs/bodyparser


- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 15 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-qcm7-3vpr-hj5h

## What is CVE-2026-48795?

CVE-2026-48795 is a high-severity vulnerability in adonisjs core, published on 15 Jul 2026. 

### Official description

AdonisJS is a TypeScript-first web framework. From 10.1.3 until 10.1.5 and 11.0.3, AdonisJS @adonisjs/bodyparser incompletely fixed CVE-2026-25754 because nested multipart field payloads such as user.__proto__.polluted and constructor.prototype still caused lodash _.set() via @poppinss/utils to create plain intermediate objects and pollute Object.prototype. This issue is fixed in versions 10.1.5 and 11.0.3.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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

4 open source packages ship an affected version, including @adonisjs/bodyparser.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@adonisjs/bodyparser` | npm | From 10.1.3 | 10.1.5 |
| `@adonisjs/bodyparser` | npm | From 10.1.3 | 10.1.5 |
| `@adonisjs/bodyparser` | npm | From 11.0.0-next.9 | 11.0.3 |
| `@adonisjs/bodyparser` | npm | From 11.0.0-next.9 | 11.0.3 |

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

Upgrade @adonisjs/bodyparser to a fixed version for your release line: 10.1.5 or 11.0.3.

## Is CVE-2026-48795 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48795 is a high-severity vulnerability in adonisjs core, published on 15 Jul 2026. 
Exploitation: There is no known exploitation of CVE-2026-48795 in the wild and no public exploit code.

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

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-48795/ (Markdown: https://insights.sbomify.com/CVE-2026-48795/index.md)
```

## Sources

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

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