axios: Improperly Controlled Modification of Dynamically-Determined Object Attributes
CVE-2026-42044 is a critical-severity improperly controlled modification of dynamically-determined object attributes vulnerability in axios, with a CVSS 3.1 base score of 9.1 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. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.62% chance of exploitation within 30 days, higher than 50% of scored CVEs.
Critical severity: a successful attack would have severe impact.
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
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.5 | Medium | CNA (github.com) |
| CVSS 3.1 | 9.1 | Critical | NVD |
| CVSS 3.1 | 7.4 | High | CNA |
Official description
Axios is a promise based HTTP client for the browser and Node.js. From 1.0.0 to before 1.15.2, he Axios library is vulnerable to a Prototype Pollution "Gadget" attack that allows any Object.prototype pollution in the application's dependency tree to be escalated into surgical, invisible modification of all JSON API responses — including privilege escalation, balance manipulation, and authorization bypass. The default transformResponse function at lib/defaults/index.js:124 calls JSON.parse(data, this.parseReviver), where this is the merged config object. Because parseReviver is not present in Axios defaults, not validated by assertOptions, and not subject to any constraints, a polluted Object.prototype.parseReviver function is called for every key-value pair in every JSON response, allowing the attacker to selectively modify individual values while leaving the rest of the response intact. This vulnerability is fixed in 1.15.2.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improperly Controlled Modification of Dynamically-Determined Object Attributes
The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.
How developers prevent this class of flaw
- If available, use features of the language or framework that allow specification of allowlists of attributes or fields that are allowed to be modified. If possible, prefer allowlists over denylists. For applications written with Ruby on Rails, use the attr_accessible (allowlist) or attr_protected (denylist) macros in each class that may be used in mass assignment.
- If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- For any externally-influenced input, check the input against an allowlist of internal object attributes or fields that are allowed to be modified.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/axios/axios/security/advisories/GHSA-3w6x-2g7m-8v23Exploit, Mitigation
Other references
- access.redhat.com/errata/RHSA-2026:16532
- access.redhat.com/errata/RHSA-2026:16534
- access.redhat.com/errata/RHSA-2026:16535
- access.redhat.com/errata/RHSA-2026:16542
- access.redhat.com/errata/RHSA-2026:17657
- access.redhat.com/errata/RHSA-2026:17699
- access.redhat.com/errata/RHSA-2026:19109
- access.redhat.com/errata/RHSA-2026:19375
- access.redhat.com/errata/RHSA-2026:20338
- access.redhat.com/errata/RHSA-2026:20454
- access.redhat.com/errata/RHSA-2026:20889
- access.redhat.com/errata/RHSA-2026:20938
- access.redhat.com/errata/RHSA-2026:21017
- access.redhat.com/errata/RHSA-2026:21338
- access.redhat.com/errata/RHSA-2026:21772
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 Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 9.1 Critical severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.