Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.3amended

Axios: Prototype Pollution Gadget in axios toFormData Options

CVE-2026-101909GHSA-x97p-jq2g-jp4f

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (axios 1.20.0, 0.34.0), 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 axios

    Affected
    >= 0.28.0, < 0.34.0>= 1.15.1, < 1.20.0
    Fixed in
    0.34.0, 1.20.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-101909: 0.50% estimated exploitation activity in the next 30 days; percentile 42.69 (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 Axios form serialization reads visitor, maxDepth, dots, indexes, metaTokens, and Blob from an internal options object without own-property guards. When Object.prototype has been polluted elsewhere in the same process, those inherited values can change how axios serializes multipart and URL-encoded request bodies. Axios does not create the prototype pollution source. This is a read-side gadget: axios turns an existing same-process pollution condition into altered request serialization or request failures. Impact The impact depends on which property is polluted and which axios serialization path the application uses. Polluted dots, indexes, or metaTokens can change field names and cause the receiving service to parse different data than the caller intended. Polluted maxDepth can cause nested form submissions to throw ERRFORMDATADEPTHEXCEEDED, producing request-level or service-level denial of service for affected workflows. Polluted visitor can execute as the serializer visitor…

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

    Amended from ghsa record GHSA-x97p-jq2g-jp4f

  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-x97p-jq2g-jp4f

  4. Revision 1 · created ·

    Published from ghsa record GHSA-x97p-jq2g-jp4f

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

Advisory: Axios: Prototype Pollution Gadget in axios toFormData Options
IDs: CVE-2026-101909, GHSA-x97p-jq2g-jp4f
Record: https://patchnext.com/advisories/cve-2026-101909 (revision 4, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: axios 1.20.0, 0.34.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm axios: affected >= 0.28.0, < 0.34.0; >= 1.15.1, < 1.20.0; fixed in 0.34.0, 1.20.0

## Suggested inspection (read-only)
- `npm ls axios --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 axios.
- 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-x97p-jq2g-jp4f (GitHub-reviewed advisory GHSA-x97p-jq2g-jp4f lists affected ranges: npm axios >=0.28.0 =1.15.1 <1.20.0)
- Verified: https://osv.dev/vulnerability/GHSA-x97p-jq2g-jp4f (OSV record GHSA-x97p-jq2g-jp4f lists affected ranges: npm axios >=0.28.0 =1.15.1 <1.20.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…