Allocation of Resources Without Limits or Throttling in Axios

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-44488: 0.67% estimated exploitation activity in the next 30 days; percentile 52.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Axios versions 1.7.0 through 1.15.x did not enforce configured request and response size limits when requests were sent with the fetch adapter. Applications that selected adapter: 'fetch', or ran in environments where axios resolved to the fetch adapter, could receive or send bodies larger than maxContentLength or maxBodyLength despite those limits being explicitly configured. This can cause resource exhaustion in server-side usage when a malicious or compromised server returns an oversized response, when an attacker can supply a large data: URL, or when an application forwards attacker-controlled request bodies through axios while relying on maxBodyLength as a boundary. Impact The impact is availability-only. Affected applications may process, buffer, or transmit data beyond the configured limit, potentially exhausting memory, CPU, or network resources. This does not affect axios’s default unlimited behaviour by itself: maxContentLength and maxBodyLength default to -1. The…

Published by the source

4 Jun 2026, 14:21 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:55 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-777c-7fjr-54vf

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-777c-7fjr-54vf

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

# Patch Next advisory brief: CVE-2026-44488

Advisory: Allocation of Resources Without Limits or Throttling in Axios
IDs: CVE-2026-44488, GHSA-777c-7fjr-54vf
Record: https://patchnext.com/advisories/cve-2026-44488 (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. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm axios: affected >= 1.7.0, < 1.16.0; fixed in 1.16.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-777c-7fjr-54vf (OSV record GHSA-777c-7fjr-54vf lists affected ranges: npm axios >=1.7.0 <1.16.0 (fixed))
- Verified: https://github.com/advisories/GHSA-777c-7fjr-54vf (GitHub-reviewed advisory GHSA-777c-7fjr-54vf lists affected ranges: npm axios >=1.7.0 <1.16.0)

Commands are suggestions: review each one before running it.