axios: Improper Check for Unusual or Exceptional Conditions
CVE-2026-25639 is a high-severity improper check for unusual or exceptional conditions vulnerability in axios, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected axios versions: >= 1.0.0, < 1.13.5; < 0.30.3. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 2.76% chance of exploitation within 30 days, higher than 86% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of axios you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (github.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (github.com) |
| CVSS 3.1 | 7.5 | High | CNA |
Official description
Axios is a promise based HTTP client for the browser and Node.js. Prior to versions 0.30.3 and 1.13.5, the mergeConfig function in axios crashes with a TypeError when processing configuration objects containing __proto__ as an own property. An attacker can trigger this by providing a malicious configuration object created via JSON.parse(), causing complete denial of service. This vulnerability is fixed in versions 0.30.3 and 1.13.5.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Check for Unusual or Exceptional Conditions
The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Choose languages with features such as exception handling that force the programmer to anticipate unusual conditions that may generate exceptions. Custom exceptions may need to be developed to handle unusual business-logic conditions. Be careful not to pass sensitive exceptions back to the user (CWE-209, CWE-248).
- Check the results of all functions that return a value and verify that the value is expected.
- If using exception handling, catch and throw specific exceptions instead of overly-general exceptions (CWE-396, CWE-397). Catch and handle exceptions as locally as possible so that exceptions do not propagate too far up the call stack (CWE-705). Avoid unchecked or uncaught exceptions where feasible (CWE-248).
More Improper Check for Unusual or Exceptional Conditions vulnerabilities (CWE-754)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Patches and release notes
- github.com/axios/axios/commit/28c721588c7a77e7503d0a434e016f852c597b57
- github.com/axios/axios/commit/d7ff1409c68168d3057fc3891f911b2b92616f9e
- github.com/axios/axios/pull/7369Issue Tracking
- github.com/axios/axios/pull/7388Issue Tracking
- github.com/axios/axios/releases/tag/v0.30.3Release Notes
- github.com/axios/axios/releases/tag/v1.13.5Product, Release Notes
Other references
- access.redhat.com/errata/RHSA-2026:10184
- access.redhat.com/errata/RHSA-2026:11414
- access.redhat.com/errata/RHSA-2026:13542
- access.redhat.com/errata/RHSA-2026:13548
- access.redhat.com/errata/RHSA-2026:19712
- access.redhat.com/errata/RHSA-2026:25041
- access.redhat.com/errata/RHSA-2026:2694
- access.redhat.com/errata/RHSA-2026:3087
- access.redhat.com/errata/RHSA-2026:3105
- access.redhat.com/errata/RHSA-2026:3106
- access.redhat.com/errata/RHSA-2026:3107
- access.redhat.com/errata/RHSA-2026:3109
- access.redhat.com/errata/RHSA-2026:36882
- access.redhat.com/errata/RHSA-2026:41064
- access.redhat.com/errata/RHSA-2026:4942
Other vulnerabilities in axios
- 8.3 High severity
- 7.0 High severity
- 8.2 High severity
- 7.6 High severity
- 8.2 High severity
- 8.2 High severity
Recent Improper Check for Unusual or Exceptional Conditions vulnerabilities
- 7.5 High severity
- 10.0 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.4 High severity
- 7.5 High severity
Spotted an error? Tell us.