Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Axios: Regular Expression Denial of Service (ReDoS) via Cookie Name Injection

CVE-2026-44496GHSA-hfxv-24rg-xrqf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (axios 1.16.0, 0.32.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
    >= 1.0.0, < 1.16.0<= 0.31.1
    Fixed in
    1.16.0, 0.32.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-44496: 5.41% estimated exploitation activity in the next 30 days; percentile 92.70 (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 versions before 0.32.0 on the 0.x line and before 1.16.0 on the 1.x line build a regular expression from the configured XSRF cookie name without escaping regex metacharacters. In standard browser environments, an attacker who can influence the cookie name passed to axios can cause expensive regex backtracking while axios reads document.cookie. The practical impact is client-side availability degradation, such as freezing the affected browser tab while axios prepares a request. The issue does not affect ordinary Node.js HTTP adapter usage, React Native, or web workers, where axios does not read document.cookie. Impact Applications are affected only when attacker-controlled data can reach the XSRF cookie name configuration or a direct/unsafe call to the internal cookie helper. This does not expose credentials, modify requests, or affect response integrity. The impact is availability only. Affected Functionality Affected code paths: - lib/helpers/cookies.js read(name) in…

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

    Amended from ghsa record GHSA-hfxv-24rg-xrqf

  2. Revision 1 · created ·

    Published from osv record GHSA-hfxv-24rg-xrqf

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

Advisory: Axios: Regular Expression Denial of Service (ReDoS) via Cookie Name Injection
IDs: CVE-2026-44496, GHSA-hfxv-24rg-xrqf
Record: https://patchnext.com/advisories/cve-2026-44496 (revision 2, source checked 26 Oct 2026, 12:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: axios 1.16.0, 0.32.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm axios: affected >= 1.0.0, < 1.16.0; <= 0.31.1; fixed in 1.16.0, 0.32.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://osv.dev/vulnerability/GHSA-hfxv-24rg-xrqf (OSV record GHSA-hfxv-24rg-xrqf lists affected ranges: npm axios >=1.0.0 =0 <0.32.0 (fixed))
- Verified: https://github.com/advisories/GHSA-hfxv-24rg-xrqf (GitHub-reviewed advisory GHSA-hfxv-24rg-xrqf lists affected ranges: npm axios >=1.0.0 =0 <=0.31.1)

Commands are suggestions: review each one before running it.

Loading voting…