Regex DoS in Axios 0.x/1.x via XSRF Cookie Name in Browser
CVE-2026-44496 Published on June 11, 2026

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.

NVD

Vulnerability Analysis

CVE-2026-44496 is exploitable with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. An automatable proof of concept (POC) exploit exists. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity, and a high impact on availability.

Attack Vector:
NETWORK
Attack Complexity:
LOW
Privileges Required:
NONE
User Interaction:
NONE
Scope:
UNCHANGED
Confidentiality Impact:
NONE
Integrity Impact:
NONE
Availability Impact:
HIGH

Weakness Types

What is a Resource Exhaustion Vulnerability?

The software does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.

CVE-2026-44496 has been classified to as a Resource Exhaustion vulnerability or weakness.

What is a ReDoS Vulnerability?

The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. Some regular expression engines have a feature called "backtracking". If the token cannot match, the engine "backtracks" to a position that may result in a different token that can match. Backtracking becomes a weakness if all of these conditions are met:

CVE-2026-44496 has been classified to as a ReDoS vulnerability or weakness.


Products Associated with CVE-2026-44496

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2026-44496 are published in these products:

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Affected Versions

axios: Red Hat Advanced Cluster Management for Kubernetes 2.13: Red Hat Advanced Cluster Management for Kubernetes 2.14: Red Hat Advanced Cluster Security for Kubernetes 4.10: Red Hat Advanced Cluster Security for Kubernetes 4.9: Red Hat Developer Hub 1.10: Red Hat Developer Hub 1.9: Red Hat Discovery 2: Red Hat OpenShift Container Platform 4.15: Red Hat OpenShift Container Platform 4.16: Red Hat OpenShift Container Platform 4.19: Red Hat OpenShift Container Platform 4.20: Red Hat OpenShift Container Platform 4.21: Red Hat OpenShift Dev Spaces 3.29: Red Hat OpenShift Service Mesh 2.6: Red Hat OpenShift Service Mesh 3.1: Red Hat OpenShift Service Mesh 3.2: Red Hat OpenShift Service Mesh 3.3: Red Hat OpenShift Service Mesh 3: Red Hat Quay 3.10: Red Hat Quay 3.12: Red Hat Quay 3.9: Red Hat multicluster engine for Kubernetes 2.8: Red Hat multicluster engine for Kubernetes 2.9: Red Hat Migration Toolkit for Applications 8: Red Hat Migration Toolkit for Containers: Red Hat Network Observability Operator: Red Hat OpenShift Pipelines: Red Hat AMQ Broker 7: Red Hat Ansible Automation Platform 2: Red Hat build of Apache Camel - HawtIO 4: Red Hat build of Apicurio Registry 3: Red Hat Build of Podman Desktop - Tech Preview: Red Hat Data Grid 8: Red Hat Enterprise Linux AI (RHEL AI) 3: Red Hat Fuse 7: Red Hat OpenShift AI (RHOAI): Red Hat OpenShift Container Platform 4: Red Hat OpenShift Virtualization 4: Red Hat Quay 3: Red Hat Trusted Artifact Signer: Red Hat Trusted Profile Analyzer: Red Hat Self-service automation portal 2: Red Hat Cryostat 4: Red Hat Gatekeeper 3: Red Hat OpenShift Service Mesh 3: Red Hat 3scale API Management Platform 2: Red Hat build of Apache Camel for Spring Boot 4: Red Hat Enterprise Linux 8: Red Hat Enterprise Linux 9: Red Hat Satellite 6:

Exploit Probability

EPSS
0.49%
Percentile
38.00%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.