LiveActive security incident?Get immediate response
CVE Record

CVE-2026-44495: Axios: Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

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.

HighCVSS 7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Axios, a widely used HTTP client library for Node.js and browsers, has a flaw that can be abused only if another vulnerability in the same application has already tampered with a shared JavaScript object. When that happens, Axios may pick up attacker-controlled values as request settings, which can leak sensitive data or alter server responses handed back to the app.

Executive priority

Prioritize as a scheduled patching cycle item, not an emergency. Exploitation requires a chained precondition, but Axios ubiquity and the volume of Red Hat errata mean most environments have exposed components. Coordinate with app teams to upgrade within the next patch window.

Technical view

Axios versions 0.19.0 through <0.31.1 and 1.0.0 through <1.15.2 contain prototype-pollution gadgets in request config processing. If Object.prototype.transformResponse is polluted upstream, Axios inherits it as configuration or option validator logic. Axios does not itself introduce the pollution; exploitation requires a separate prototype-pollution primitive. Fixed in 0.31.1 and 1.15.2 per the vendor advisory.

Likely exposure

Broad. Axios is one of the most widely deployed Node.js and browser HTTP clients, and Red Hat has issued numerous RHSA errata indicating downstream product exposure. Actual risk depends on whether a co-resident prototype-pollution flaw exists in the same JS process.

Exploitation context

Not listed in CISA KEV and no public reports of in-the-wild exploitation in the provided sources. CVSS is 7.0 with high attack complexity, reflecting the precondition of a separate prototype-pollution vulnerability. The chain enables credential theft or response hijacking rather than direct RCE.

Researcher notes

Gadget CWEs are CWE-1321, CWE-915, and CWE-94. Focus code review on Axios config merge paths and any transformResponse consumers. Exploit chain requires attacker-controlled Object.prototype pollution earlier in the same JS process, so pair triage with review of any known prototype-pollution issues in co-resident libraries. Red Hat CSAF VEX file provides authoritative product-level status.

Mitigation direction

  • Upgrade Axios to 1.15.2 (1.x line) or 0.31.1 (legacy 0.x line) across all services.
  • Apply Red Hat RHSA errata for affected products where Axios is bundled.
  • Audit dependencies for known prototype-pollution CVEs and patch those root causes.
  • Freeze or sanitize Object.prototype where feasible in Node.js runtimes handling untrusted input.
  • Enforce SCA gates in CI to block reintroduction of vulnerable Axios ranges.

Validation and detection

  • Run npm ls axios or yarn why axios to enumerate direct and transitive versions.
  • Confirm resolved versions are >=1.15.2 or >=0.31.1 in lockfiles after upgrade.
  • Check Red Hat product inventory against the cited RHSA advisories for applied errata.
  • Review SBOMs and container images for older Axios copies in nested node_modules.
  • Re-run SCA scanners (Trivy, Snyk, GHAS) to verify GHSA-3g43-6gmg-66jw is cleared.
Prepared
Confidence
high
Sources
9

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
cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-44495 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 (3.1)
Known Exploited
No
Published

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

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
29Source links

SSVC decision data

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

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
7CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L2.24.7GitHub_M
7CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L2.24.7redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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: Information disclosure due to prototype pollution vulnerability
other:Red Hat severity ratingcvssV3_1
  • 2026-06-11T17:00:53.999Z: Reported to Red Hat.
  • 2026-06-11T15:33:12.433Z: Made public.

Source materials

Affected products

Products and packages named in the record

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

CWE details

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

CWE-1321 · source CWE mapping

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-915 · source CWE mapping

Improperly Controlled Modification of Dynamically-Determined Object Attributes

Improperly Controlled Modification of Dynamically-Determined Object Attributes represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.