Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.2amended

AdonisJS multipart body parsing has Prototype Pollution issue

CVE-2026-25754GHSA-f5x2-vj4h-vg4c

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@adonisjs/bodyparser 11.0.0-next.9, 10.1.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @adonisjs/bodyparser

    Affected
    <= 10.1.2>= 11.0.0-next.0, <= 11.0.0-next.8
    Fixed in
    11.0.0-next.9, 10.1.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
EPSS
  • CVE-2026-25754: 0.42% estimated exploitation activity in the next 30 days; percentile 36.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Description A Prototype Pollution vulnerability (CWE-1321) in AdonisJS multipart form-data parsing may allow a remote attacker to manipulate object prototypes at runtime. This impacts @adonisjs/bodyparser through version 10.1.2 and 11.x prerelease versions prior to 11.0.0-next.8. This issue has been patched in @adonisjs/bodyparser versions 10.1.3 and 11.0.0-next.9 Details AdonisJS parses multipart/form-data requests via the BodyParser package. During multipart parsing, form field names are used to construct plain JavaScript objects representing the parsed request body. Due to insufficient validation of multipart field names, specially crafted fields containing reserved property names such as proto, constructor, or prototype could be assigned directly to objects created during parsing. This allows an attacker to pollute object prototypes, potentially affecting other parts of the application that rely on these objects. The vulnerability is limited to multipart request parsing and does…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-f5x2-vj4h-vg4c

  2. Revision 1 · created ·

    Published from osv record GHSA-f5x2-vj4h-vg4c

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25754

Advisory: AdonisJS multipart body parsing has Prototype Pollution issue
IDs: CVE-2026-25754, GHSA-f5x2-vj4h-vg4c
Record: https://patchnext.com/advisories/cve-2026-25754 (revision 2, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @adonisjs/bodyparser 11.0.0-next.9, 10.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @adonisjs/bodyparser: affected <= 10.1.2; >= 11.0.0-next.0, <= 11.0.0-next.8; fixed in 11.0.0-next.9, 10.1.3

## Suggested inspection (read-only)
- `npm ls @adonisjs/bodyparser --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @adonisjs/bodyparser.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-f5x2-vj4h-vg4c (OSV record GHSA-f5x2-vj4h-vg4c lists affected ranges: npm @adonisjs/bodyparser >=0 =11.0.0-next.0 <11.0.0-next.9 (fixed))
- Verified: https://github.com/advisories/GHSA-f5x2-vj4h-vg4c (GitHub-reviewed advisory GHSA-f5x2-vj4h-vg4c lists affected ranges: npm @adonisjs/bodyparser >=0 =11.0.0-next.0 <=11.0.0-next.8)

Commands are suggestions: review each one before running it.

Loading voting…