axios: Improper Control of Generation of Code
CVE-2026-44495 is a high-severity improper control of generation of code vulnerability in axios, with a CVSS 3.1 base score of 7.7 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.15.2; >= 0.19.0, < 0.31.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.85% chance of exploitation within 30 days, higher than 59% 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
- HighSuccess depends on conditions outside the attacker's control.
- 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
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.0 | High | CNA (github.com) |
| CVSS 3.1 | 7.7 | High | NVD |
| CVSS 3.1 | 7.0 | High | CNA |
Official description
Axios is a promise based HTTP client for the browser and Node.js. From 0.19.0 to before 0.31.1 and 1.15.2, Axios contains prototype-pollution gadgets in request config processing. If another vulnerability in the same JavaScript process has already polluted Object.prototype.transformResponse, affected Axios versions may treat that inherited value as request configuration or as an option validator. Axios does not itself create the prototype pollution. Exploitability requires a separate prototype-pollution vulnerability or equivalent attacker control over Object.prototype before Axios creates a request. This vulnerability is fixed in 0.31.1 and 1.15.2.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- access.redhat.com/errata/RHSA-2026:20889Third Party Advisory
- access.redhat.com/errata/RHSA-2026:20938Third Party Advisory
- access.redhat.com/errata/RHSA-2026:27044Third Party Advisory
- access.redhat.com/errata/RHSA-2026:27063Third Party Advisory
- access.redhat.com/errata/RHSA-2026:27944Third Party Advisory
- access.redhat.com/errata/RHSA-2026:28964Third Party Advisory
- access.redhat.com/errata/RHSA-2026:29082Third Party Advisory
- access.redhat.com/errata/RHSA-2026:29197Third Party Advisory
- access.redhat.com/errata/RHSA-2026:30650Third Party Advisory
- access.redhat.com/errata/RHSA-2026:30651Third Party Advisory
- access.redhat.com/errata/RHSA-2026:33155Third Party Advisory
- access.redhat.com/errata/RHSA-2026:33160Third Party Advisory
- access.redhat.com/errata/RHSA-2026:33163Third Party Advisory
- access.redhat.com/errata/RHSA-2026:33173Third Party Advisory
- access.redhat.com/errata/RHSA-2026:33183Third Party Advisory
Other references
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 Control of Generation of Code vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
- 7.8 High severity
- 8.1 High severity
Spotted an error? Tell us.