LiveActive security incident?Get immediate response
CVE Record

CVE-2026-44496: Axios: Regular Expression Denial of Service (ReDoS) via Cookie Name Injection

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

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a browser-side denial-of-service issue in Axios. A bad XSRF cookie-name configuration can make Axios spend excessive CPU reading cookies, potentially freezing a user’s browser tab before a request is sent. The source bundle identifies fixed Axios versions and does not indicate confirmed exploitation in the wild.

Executive priority

Prioritize remediation for customer-facing web applications that bundle affected Axios and rely on browser XSRF cookie handling. Treat as high availability risk, but scope carefully because the bundle excludes ordinary Node.js, React Native, and web worker usage.

Technical view

Axios before 0.32.0 on 0.x and before 1.16.0 on 1.x builds a regex from xsrfCookieName without escaping regex metacharacters. In standard browser environments, attacker influence over that configured cookie name can trigger expensive regex backtracking against document.cookie. Ordinary Node.js adapter usage, React Native, and web workers are stated as unaffected.

Likely exposure

Exposure is most likely in web applications bundling affected Axios versions and using browser XSRF cookie handling where the cookie-name configuration can be influenced directly or indirectly. Server-side Node.js-only Axios usage is not indicated as affected by the bundle.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. Practical impact is availability degradation in the browser, such as a frozen tab. The attack requires influence over the Axios XSRF cookie name, so real-world reach depends on application configuration paths.

Researcher notes

The key condition is attacker influence over the configured XSRF cookie name, not merely setting an arbitrary cookie value. Evidence in the bundle supports ReDoS during document.cookie processing. Downstream product impact should be validated through dependency provenance and Red Hat advisory applicability.

Mitigation direction

  • Upgrade Axios 1.x deployments to 1.16.0 or later.
  • Upgrade Axios 0.x deployments to 0.32.0 or later.
  • Review Red Hat advisories if consuming Axios through Red Hat-packaged products.
  • Prevent untrusted input from controlling Axios XSRF cookie-name configuration.
  • Check vendor guidance for any packaged or transitive dependency constraints.

Validation and detection

  • Inventory direct and transitive Axios versions in application dependency manifests and SBOMs.
  • Confirm deployed browser bundles contain Axios 1.16.0, 0.32.0, or later fixed versions.
  • Identify browser code paths using Axios XSRF cookie handling.
  • Review configuration sources for xsrfCookieName to ensure they are trusted.
  • Confirm Node.js-only, React Native, or web worker uses are not misclassified as browser exposure.
Prepared
Confidence
medium
Sources
8

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-1333: 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
cwe · low confidence lookup

CWE-400: 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-44496 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
33Source 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-44496Attack 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: Client-side Denial of Service via unescaped regex metacharacters in XSRF cookie name
other:Red Hat severity ratingcvssV3_1
  • 2026-06-11T17:01:15.856Z: Reported to Red Hat.
  • 2026-06-11T15:34:28.492Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
axiosaxios>= 1.0.0, < 1.16.0, < 0.32.0Listed
Weakness

CWE details

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

CWE-1333 · source CWE mapping

Inefficient Regular Expression Complexity

Inefficient Regular Expression Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.