Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.2amended

AdonisJS Path Traversal in Multipart File Handling

CVE-2026-21440GHSA-gvq6-hvvp-h34h

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@adonisjs/bodyparser 11.0.0-next.6, 10.1.2), 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.6
    Fixed in
    10.1.2, 11.0.0-next.6

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-21440: 1.03% estimated exploitation activity in the next 30 days; percentile 63.88 (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 Description A Path Traversal (CWE-22) vulnerability in AdonisJS multipart file handling may allow a remote attacker to write arbitrary files to arbitrary locations on the server filesystem. This impacts @adonisjs/bodyparser through version 10.1.1 and 11.x prerelease versions prior to 11.0.0-next.6. This issue has been patched in @adonisjs/bodyparser versions 10.1.2 and 11.0.0-next.6. Details AdonisJS parses multipart/form-data via BodyParser and exposes uploads as MultipartFile. The issue is in the MultipartFile.move(location, options) default options. If options.name isn't provided, it defaults to the unsanitized client filename and builds the destination with path.join(location, name), allowing a traversal to escape the default or intended directory chosen by the developer. If options.overwrite isn't provided, it defaults to true, allowing file overwrites. The documentation previously demonstrated examples leading developers to this vulnerable code path. Impact Exploitation…

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

    Amended from ghsa record GHSA-gvq6-hvvp-h34h

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-gvq6-hvvp-h34h

  4. Revision 1 · created ·

    Published from ghsa record GHSA-gvq6-hvvp-h34h

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

Advisory: AdonisJS Path Traversal in Multipart File Handling
IDs: CVE-2026-21440, GHSA-gvq6-hvvp-h34h
Record: https://patchnext.com/advisories/cve-2026-21440 (revision 4, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.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.6, 10.1.2. 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.6; fixed in 10.1.2, 11.0.0-next.6

## 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://github.com/advisories/GHSA-gvq6-hvvp-h34h (GitHub-reviewed advisory GHSA-gvq6-hvvp-h34h lists affected ranges: npm @adonisjs/bodyparser >=0 =11.0.0-next.0 <11.0.0-next.6)
- Verified: https://osv.dev/vulnerability/GHSA-gvq6-hvvp-h34h (OSV record GHSA-gvq6-hvvp-h34h lists affected ranges: npm @adonisjs/bodyparser >=0 =11.0.0-next.0 <11.0.0-next.6 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…