Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.6amended

@adonisjs/bodyparser has an incomplete fix for CVE-2026-25754

CVE-2026-48795GHSA-qcm7-3vpr-hj5h

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@adonisjs/bodyparser 11.0.3, 10.1.5), 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.3, <= 10.1.4>= 11.0.0-next.9, <= 11.0.1
    Fixed in
    10.1.5, 11.0.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
EPSS
  • CVE-2026-48795: 0.55% estimated exploitation activity in the next 30 days; percentile 45.87 (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.

Summary The fix for GHSA-f5x2-vj4h-vg4c / CVE-2026-25754 introduced in commit 40e1c71 is incomplete and can be bypassed through nested prototype pollution payloads. The original patch replaced the internal FormFields storage object with Object.create(null), preventing direct payloads such as proto.polluted. However, payloads containing a non-dangerous segment before proto or constructor.prototype, such as user.proto.polluted, still lead to Object.prototype pollution. This issue is exploitable remotely through a single unauthenticated multipart/form-data request using the default configuration. Affected versions - = 10.1.3 < 10.1.5 - = 11.0.0-next.9 < 11.0.3 Details The regression tests added by the original fix only covered direct payloads such as: - proto.polluted - constructor.prototype.polluted These payloads are blocked because the root object no longer inherits from Object.prototype. However, lodash .set() (via @poppinss/utils) still creates intermediate objects using plain {}…

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

    Amended from ghsa record GHSA-qcm7-3vpr-hj5h

  2. Revision 1 · created ·

    Published from osv record GHSA-qcm7-3vpr-hj5h

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-48795

Advisory: @adonisjs/bodyparser has an incomplete fix for CVE-2026-25754
IDs: CVE-2026-48795, GHSA-qcm7-3vpr-hj5h
Record: https://patchnext.com/advisories/cve-2026-48795 (revision 2, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
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.3, 10.1.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @adonisjs/bodyparser: affected >= 10.1.3, <= 10.1.4; >= 11.0.0-next.9, <= 11.0.1; fixed in 10.1.5, 11.0.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-qcm7-3vpr-hj5h (OSV record GHSA-qcm7-3vpr-hj5h lists affected ranges: npm @adonisjs/bodyparser >=10.1.3 =11.0.0-next.9 <11.0.3 (fixed))
- Verified: https://github.com/advisories/GHSA-qcm7-3vpr-hj5h (GitHub-reviewed advisory GHSA-qcm7-3vpr-hj5h lists affected ranges: npm @adonisjs/bodyparser >=10.1.3 =11.0.0-next.9 <=11.0.1)

Commands are suggestions: review each one before running it.

Loading voting…