CVE-2026-42264

CRITICALNVD 9.17.4
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% 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
Trending — 3 sources updated this weekElevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.1Exploit: 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. From version 1.0.0 to before version 1.15.2, fFive config properties (auth, baseURL, socketPath, beforeRedirect, and insecureHTTPParser) in the HTTP adapter are read via direct property access without hasOwnProperty guards, making them exploitable as prototype pollution gadgets. When Object.prototype is polluted by another dependency in the same process, axios silently picks up these polluted values on every outbound HTTP request. This issue has been patched in version 1.15.2.

CVSS v3
9.1
EG Score
7.4(medium)
EPSS
49.9%
KEV
Not listed

Published

May 8, 2026

Last Modified

July 21, 2026

Advisory Details (4)

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

Prototype pollution read-side gadgets in HTTP adapter allow credential injection and request hijacking · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-q8qp-cvcw-x6jj
generic

Release v1.15.2 · axios/axios · GitHub

https://github.com/axios/axios/releases/tag/v1.15.2
generic

fix: more header pollutions by jasonsaayman · Pull Request #10779 · axios/axios · GitHub

https://github.com/axios/axios/pull/10779
generic

fix: more header pollutions (#10779) · axios/axios@4791514 · GitHub

https://github.com/axios/axios/commit/47915144662f2733e6c051bdcb895a8c8f0586aa

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
axios1.15.2

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 45× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-20 12:37 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-16 09:53 UTCOSV refresh
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 11:54 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  12. 2026-07-15 02:25 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  15. 2026-07-13 22:30 UTCEPSS rescore
  16. 2026-07-13 14:08 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  17. 2026-07-13 12:52 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-10 12:26 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  22. 2026-07-10 12:12 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-08 15:15 UTCEPSS rescore
  25. 2026-07-08 14:36 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
Show 71 more
  1. 2026-07-08 12:47 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  2. 2026-07-07 13:46 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 13:51 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  6. 2026-07-06 13:07 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 04:33 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-24 14:05 UTCEPSS rescore
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
  26. 2026-06-19 19:25 UTCEPSS rescore
  27. 2026-06-18 17:52 UTCEPSS rescore
  28. 2026-06-18 17:52 UTCEPSS rescore
  29. 2026-06-17 17:53 UTCEPSS rescore
  30. 2026-06-16 17:52 UTCEPSS rescore
  31. 2026-06-15 17:49 UTCEPSS rescore
  32. 2026-06-13 23:00 UTCEPSS rescore
  33. 2026-06-12 23:12 UTCEPSS rescore
  34. 2026-06-12 23:12 UTCEPSS rescore
  35. 2026-06-11 14:00 UTCEPSS rescore
  36. 2026-06-10 22:18 UTCEPSS rescore
  37. 2026-06-10 13:22 UTCEPSS rescore
  38. 2026-06-10 13:22 UTCEPSS rescore
  39. 2026-06-08 14:17 UTCEPSS rescore
  40. 2026-06-08 14:17 UTCEPSS rescore
  41. 2026-06-07 15:25 UTCEPSS rescore
  42. 2026-06-07 15:25 UTCEPSS rescore
  43. 2026-06-06 13:47 UTCEPSS rescore
  44. 2026-06-06 13:47 UTCEPSS rescore
  45. 2026-06-05 22:47 UTCEPSS rescore
  46. 2026-06-05 06:10 UTCEPSS rescore
  47. 2026-06-05 06:10 UTCEPSS rescore
  48. 2026-06-04 13:12 UTCEPSS rescore
  49. 2026-06-04 13:12 UTCEPSS rescore
  50. 2026-06-02 20:13 UTCEPSS rescore
  51. 2026-06-01 13:52 UTCEPSS rescore
  52. 2026-06-01 13:52 UTCEPSS rescore
  53. 2026-05-31 22:30 UTCEPSS rescore
  54. 2026-05-31 22:30 UTCEPSS rescore
  55. 2026-05-31 00:16 UTCEPSS rescore
  56. 2026-05-31 00:16 UTCEPSS rescore
  57. 2026-05-29 13:44 UTCEPSS rescore
  58. 2026-05-29 13:44 UTCEPSS rescore
  59. 2026-05-28 13:44 UTCEPSS rescore
  60. 2026-05-28 13:44 UTCEPSS rescore
  61. 2026-05-28 13:44 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-27 13:40 UTCEPSS rescore
  64. 2026-05-27 13:40 UTCEPSS rescore
  65. 2026-05-26 07:18 UTCEPSS rescore
  66. 2026-05-26 07:18 UTCEPSS rescore
  67. 2026-05-20 22:38 UTCEPSS rescore
  68. 2026-05-20 22:38 UTCEPSS rescore
  69. 2026-05-20 13:49 UTCEG score recompute
  70. 2026-05-20 11:22 UTCEPSS rescore
  71. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-42264?
CVE-2026-42264 is a critical vulnerability published on May 8, 2026. Axios is a promise based HTTP client for the browser and Node.js. From version 1.0.0 to before version 1.15.2, fFive config properties (auth, baseURL, socketPath, beforeRedirect, and insecureHTTPParser) in the HTTP adapter are read via direct property access without hasOwnProperty guards, making…
When was CVE-2026-42264 disclosed?
CVE-2026-42264 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42264 actively exploited?
CVE-2026-42264 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 49.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42264?
CVE-2026-42264 has a CVSS v3 base score of 9.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.4.
How do I remediate CVE-2026-42264?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42264, 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-42264

Explore →

Is Your Infrastructure Affected by CVE-2026-42264?

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