LiveActive security incident?Get immediate response
CVE Record

CVE-2026-44488: Axios: Allocation of Resources Without Limits or Throttling in axios

Axios is a promise based HTTP client for the browser and Node.js. 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. This vulnerability is fixed in 0.32.0 and 1.16.0.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Axios may ignore configured request and response size limits when using its fetch adapter. A system that trusts those limits could process oversized data and exhaust memory or other resources. The primary business risk is service disruption, not data theft.

Executive priority

Treat as high priority for services where availability matters. Patch affected axios deployments promptly, starting with server-side and internet-facing systems. This is less urgent for systems that do not use axios fetch-adapter paths.

Technical view

CVE-2026-44488 is CWE-770 resource exhaustion in axios 1.7.0 through 1.15.x. With adapter: 'fetch', or environments resolving to fetch, maxContentLength and maxBodyLength may not constrain bodies. Fixed versions are listed as 0.32.0 and 1.16.0.

Likely exposure

Highest exposure is server-side JavaScript using axios with the fetch adapter, especially when contacting untrusted services, accepting attacker-controlled data: URLs, or forwarding user-controlled bodies while relying on axios size limits.

Exploitation context

The bundle does not show CISA KEV listing or cited active exploitation. Exploitation would require causing an affected application to send or receive oversized content through axios fetch-adapter paths.

Researcher notes

Evidence supports availability impact only. The affected behavior is specific to axios fetch-adapter handling of configured body limits. The source bundle does not provide exploit proof, KEV status, or broader affected product claims beyond listed axios and Red Hat references.

Mitigation direction

  • Upgrade axios to 1.16.0 or the fixed 0.32.0 line where applicable.
  • Review GitHub and Red Hat advisories for product-specific guidance.
  • Do not rely on affected axios size limits before upgrading.
  • Prioritize internet-facing server-side services and request-forwarding components.
  • Track Red Hat errata if consuming axios through Red Hat products.

Validation and detection

  • Inventory axios versions in application manifests and SBOMs.
  • Identify code setting adapter: 'fetch' or environments resolving axios to fetch.
  • Review uses of maxContentLength and maxBodyLength as security boundaries.
  • Check services that fetch untrusted URLs or forward user-controlled request bodies.
  • Confirm deployed artifacts include fixed axios versions.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-44488 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
36Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6GitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-44488Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPaxios: Axios: Denial of Service due to unenforced request and response size limits
other:Red Hat severity ratingcvssV3_1
  • 2026-06-11T17:01:36.836Z: Reported to Red Hat.
  • 2026-06-11T15:37:38.013Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
axiosaxios>= 1.7.0, < 1.16.0Listed
Weakness

CWE details

CWE-770

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs