CVE-2026-42264 Vulnerability Analysis & Exploit Details

CVE-2026-42264
Vulnerability Scoring

7.4
/10
Very High Risk

Highly exploitable, CVE-2026-42264 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-42264 Details

Status: Analyzed

Last updated: 🕠 13 May 2026, 17:53 UTC
Originally published on: 🕓 08 May 2026, 04:16 UTC

Time between publication and last update: 5 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-42264 Vulnerability Summary

CVE-2026-42264: Axios is a promise based HTTP client for the browser and Node.js. From version 1.0.0 to before version 1.15.2, fFive config properties (auth, baseURL, socketPath, beforeRedirect, and insecureHTTPParser) in the HTTP adapter are read via direct property access without hasOwnProperty guards, making them exploitable as prototype pollution gadgets. When Object.prototype is polluted by another dependency in the same process, axios silently picks up these polluted values on every outbound HTTP request. This issue has been patched in version 1.15.2.

Assessing the Risk of CVE-2026-42264

Access Complexity Graph

The exploitability of CVE-2026-42264 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-42264

CVE-2026-42264 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-42264, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-42264, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-42264 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-42264 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2026-42264 does not impact system availability.

CVE-2026-42264 References

External References

CWE Common Weakness Enumeration

CWE-1321

CAPEC Common Attack Pattern Enumeration and Classification

  • Accessing Functionality Not Properly Constrained by ACLs CAPEC-1 In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.
  • Exploiting Incorrectly Configured Access Control Security Levels CAPEC-180 An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack.
  • Manipulating User-Controlled Variables CAPEC-77 This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.

Vulnerable Configurations

  • cpe:2.3:a:axios:axios:1.0.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.0.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.0.0:alpha1:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.0.0:alpha1:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.2.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.2.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.2.0:alpha1:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.2.0:alpha1:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.2.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.2.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.2.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.2.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.2.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.2.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.3.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.3.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.3.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.3.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.3.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.3.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.3.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.3.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.5.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.5.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.6.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.6.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.6.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.6.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.6.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.6.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.6.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.6.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.6.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.6.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.6.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.6.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.6.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.6.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.6.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.6.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.0:beta0:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.0:beta0:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.0:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.7.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.7.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.8.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.8.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.8.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.8.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.8.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.8.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.8.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.8.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.8.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.8.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.9.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.9.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.10.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.10.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.11.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.11.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.12.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.12.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.12.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.12.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.12.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.12.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.13.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.13.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.13.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.13.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.13.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.13.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.13.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.13.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.13.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.13.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.13.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.13.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.13.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.13.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.14.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.14.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:axios:axios:1.15.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:axios:axios:1.15.0:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2026-42264: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-8206 – The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to privilege escalation via account takeover in ...
  • CVE-2026-3198 – MLflow 3.9.0 with basic-auth (`--app-name basic-auth`) fails to enforce authorization checks for multiple Gateway API 'list' endpoints. Specificall...
  • CVE-2026-10583 – A security vulnerability has been detected in nextlevelbuilder GoClaw up to 3.11.3. Affected by this issue is the function Import of the file inter...
  • CVE-2026-10581 – A flaw has been found in DedeCMS 5.7.88. Affected by this vulnerability is the function base64_decode of the file /plus/download.php?open=1. This m...
  • CVE-2026-3871 – A buffer overflow vulnerability in the UPnP DeletePortMapping() command in Zyxel VMG4005-B50B firmware versions through 5.13(ABRL.5.4)C0 could allo...