LiveActive security incident?Get immediate response
CVE Record

CVE-2026-42044: Axios: Invisible JSON Response Tampering via Prototype Pollution Gadget in `parseReviver`

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.

HighCVSS 7.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Axios versions 1.0.0 before 1.15.2 can let an existing prototype pollution issue silently alter JSON API responses. Business impact could include wrong authorization, privilege, or financial decisions based on tampered response data. The flaw is high severity, but exploitation depends on a separate pollution path already present in the application or dependencies.

Executive priority

Prioritize remediation in applications that make access-control, account, balance, or entitlement decisions from JSON API responses. Treat as urgent where axios is exposed alongside unpatched prototype pollution risks.

Technical view

Axios default transformResponse calls JSON.parse(data, this.parseReviver). Because parseReviver is taken from merged config and not constrained, a polluted Object.prototype.parseReviver can run on every JSON response key/value. This is described as a prototype pollution gadget, not necessarily the original pollution source. Affected axios versions are >=1.0.0 and <1.15.2; fixed in 1.15.2.

Likely exposure

Applications using axios 1.0.0 through 1.15.1 for JSON API handling are potentially exposed, especially if any dependency can pollute Object.prototype. Browser and Node.js usage are both relevant because axios supports both environments.

Exploitation context

No CISA KEV listing is indicated, and the provided sources do not state active exploitation. Attack feasibility is constrained by the need for an existing prototype pollution condition, reflected by CVSS attack complexity high.

Researcher notes

The issue is a gadget: impact depends on a separate path to Object.prototype pollution. Validate whether applications or dependencies can introduce parseReviver on Object.prototype, but avoid assuming exploitability from axios presence alone.

Mitigation direction

  • Upgrade axios to version 1.15.2 or later.
  • Regenerate lockfiles and redeploy applications that bundle axios.
  • Review Red Hat advisories if axios is consumed through Red Hat products.
  • Check vendor guidance for product-specific backports or mitigations.
  • Audit dependencies for known prototype pollution vulnerabilities.

Validation and detection

  • Inventory direct and transitive axios versions in package manifests and lockfiles.
  • Confirm runtime bundles no longer include axios versions below 1.15.2.
  • Review SCA results for CVE-2026-42044 and related prototype pollution issues.
  • Verify Red Hat package status against applicable RHSA advisories.
  • Test application authorization and financial workflows after dependency updates.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1321: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-915: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-42044 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
41Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2redhat-SADP
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N2.24.2GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2026-42044Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPaxios: Axios: Invisible JSON Response Tampering via Prototype Pollution Gadget
other:Red Hat severity ratingcvssV3_1
  • 2026-04-24T19:01:13.418Z: Reported to Red Hat.
  • 2026-04-24T17:49:49.517Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
axiosaxios>= 1.0.0, < 1.15.2Listed
Weakness

CWE details

CWE-1321CWE-915

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.