Cyber Resilience

CVE-2026-44490

Axios ≤ 0.32.0

Public PoC
Published
11 June 2026
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 4.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
EPSS Score 0.0029 21th percentile
Risk Priority 39 floored blend · peak EPSS

Summary

CVE-2026-44490 is a medium-severity Prototype Pollution (CWE-1321) vulnerability in Axios Axios. Its CVSS base score is 4.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

EU & UK References

Vulnerability Data

Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, axios exposes two read-side prototype-pollution gadgets. When Object.prototype is polluted by an upstream dependency in the same process (e.g. lodash _.merge / CVE-2018-16487),…

more

axios silently picks up the polluted values. (1) lib/utils.js line 406 builds merge()'s accumulator as result = {}, so result[targetKey] (line 414) walks Object.prototype and the polluted bucket's own keys are copied into the merged headers and ride out on the wire. (2) lib/core/mergeConfig.js line 26 builds the hasOwnProperty descriptor as a plain-object literal. Object.defineProperty reads descriptor.get/descriptor.set via the prototype chain, so a polluted Object.prototype.get or Object.prototype.set makes the call throw TypeError synchronously on every axios request. This vulnerability is fixed in 0.32.0 and 1.16.0.

CWE(s)
CWE-1321

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-42035Same product: Axios Axios
CVE-2026-44489Same product: Axios Axios
CVE-2026-42044Same product: Axios Axios
CVE-2026-42264Same product: Axios Axios
CVE-2026-42033Same product: Axios Axios
CVE-2026-44494Same product: Axios Axios
CVE-2026-42040Same product: Axios Axios
CVE-2026-42041Same product: Axios Axios
CVE-2024-39338Same product: Axios Axios
CVE-2025-27152Same product: Axios Axios

Affected Assets

axios
axios
≤ 0.32.0 · 1.0.0 — 1.16.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.3.6

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches prototype-pollution flaws before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.

A.8.32 Change management partial match
prevents

Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.

References