CVE-2026-44490

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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), 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.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
20.7%
KEV
Not listed

Published

May 29, 2026

Last Modified

June 15, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

DoS & Header Injection via Prototype Pollution Read-Side Gadgets in axios merge functions · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-898c-q2cr-xwhg

Vendor Advisories for CVE-2026-44490(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
axios—0.32.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 01:59 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-14 14:09 UTCEG score recompute
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 17:34 UTCEG score recompute
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 17:26 UTCEG score recompute
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-02 20:01 UTCEG score recompute
  18. 2026-07-02 04:26 UTCEG score recompute
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 14:03 UTCEG score recompute
  21. 2026-07-01 01:33 UTCEG score recompute
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 01:25 UTCEG score recompute
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 12:56 UTCEG score recompute
Show 52 more
  1. 2026-06-28 19:04 UTCEG score recompute
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 06:34 UTCEG score recompute
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 17:51 UTCEG score recompute
  6. 2026-06-27 05:22 UTCEG score recompute
  7. 2026-06-27 03:08 UTCEPSS rescore
  8. 2026-06-26 16:18 UTCEG score recompute
  9. 2026-06-25 18:54 UTCEG score recompute
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-25 06:24 UTCEG score recompute
  13. 2026-06-24 15:25 UTCEG score recompute
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-23 21:33 UTCEPSS rescore
  16. 2026-06-22 14:25 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-21 14:56 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 01:59 UTCEPSS rescore
  21. 2026-06-19 19:25 UTCEPSS rescore
  22. 2026-06-18 22:28 UTCEG score recompute
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-18 01:23 UTCEG score recompute
  26. 2026-06-17 17:53 UTCEPSS rescore
  27. 2026-06-17 12:29 UTCEG score recompute
  28. 2026-06-16 23:45 UTCEG score recompute
  29. 2026-06-16 17:52 UTCEPSS rescore
  30. 2026-06-16 11:16 UTCEG score recompute▲ 3.40
  31. 2026-06-15 17:49 UTCEPSS rescore
  32. 2026-06-15 17:29 UTCNVD updateCVSS v3 → 8.2 · severity → HIGH
  33. 2026-06-15 12:27 UTCEG score recompute
  34. 2026-06-14 11:27 UTCEG score recompute
  35. 2026-06-13 23:00 UTCEPSS rescore
  36. 2026-06-13 12:38 UTCEG score recompute
  37. 2026-06-12 23:12 UTCEPSS rescore
  38. 2026-06-12 23:12 UTCEPSS rescore
  39. 2026-06-12 13:46 UTCEG score recompute
  40. 2026-06-11 14:56 UTCEG score recompute
  41. 2026-06-10 16:06 UTCEG score recompute
  42. 2026-06-09 17:17 UTCEG score recompute
  43. 2026-06-08 18:27 UTCEG score recompute
  44. 2026-06-07 16:35 UTCEG score recompute
  45. 2026-06-06 17:45 UTCEG score recompute
  46. 2026-06-05 18:55 UTCEG score recompute
  47. 2026-06-04 20:05 UTCEG score recompute
  48. 2026-06-03 21:15 UTCEG score recompute
  49. 2026-06-02 22:25 UTCEG score recompute
  50. 2026-06-01 23:35 UTCEG score recompute
  51. 2026-06-01 00:46 UTCEG score recompute
  52. 2026-05-29 16:21 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44490?
CVE-2026-44490 is a high vulnerability published on May 29, 2026. 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), axios silently picks up the…
When was CVE-2026-44490 disclosed?
CVE-2026-44490 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44490 actively exploited?
CVE-2026-44490 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44490?
CVE-2026-44490 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-44490?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44490, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44490

Explore →

Is Your Infrastructure Affected by CVE-2026-44490?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs