CVE-2026-42033

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 81% 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
Elevated
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.4Exploit: NoneExposed: 0

A fix is available — apply it.

Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, when Object.prototype has been polluted by any co-dependency with keys that axios reads without a hasOwnProperty guard, an attacker can (a) silently intercept and modify every JSON response before the application sees it, or (b) fully hijack the underlying HTTP transport, gaining access to request credentials, headers, and body. The precondition is prototype pollution from a separate source in the same process. This vulnerability is fixed in 1.15.1 and 0.31.1.

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

Published

April 24, 2026

Last Modified

July 10, 2026

Advisory Details (1)

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

Prototype Pollution Gadgets in axios: Response Tampering, Data Exfiltration, and Request Hijacking · Advisory · axios/axios · GitHub

Affected: v1.13.5) addressed a separate class: passing

https://github.com/axios/axios/security/advisories/GHSA-pf86-5x62-jrwf

Patch Availability(29)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmulticluster-engine/console-mce-rhel9:17809108882026-06-11redhat
redhatrhacm2/console-rhel9:17806008232026-06-11redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17804671472026-06-10redhat
redhataxios2026-06-10redhat
redhatrhmtc/openshift-migration-ui-rhel8:17805907172026-06-10redhat
redhatquay/quay-rhel8:17808913952026-06-09redhat
redhatrhacm2/console-rhel9:17808767342026-06-08redhat
redhatmulticluster-engine/console-mce-rhel9:17809175312026-06-08redhat
redhatquay/quay-rhel8:17798114732026-06-04redhat
redhatquay/quay-rhel8:17798222612026-06-03redhat
redhatquay/quay-rhel8:17798114122026-06-02redhat
redhatquay/quay-rhel9:17799222052026-06-02redhat
redhatdevspaces/dashboard-rhel9:17793412892026-05-28redhat
redhatrhdh/rhdh-hub-rhel9:17798415862026-05-27redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17792930132026-05-26redhat
redhatquay/quay-rhel8:17796893922026-05-26redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17793715942026-05-26redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17786450992026-05-20redhat
redhatmulticluster-engine/console-mce-rhel9:17785326102026-05-19redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17785393382026-05-19redhat
redhatquay/quay-rhel9:17792040862026-05-19redhat
redhatmulticluster-engine/console-mce-rhel9:17785113482026-05-14redhat
redhatmulticluster-engine/console-mce-rhel9:17783838632026-05-14redhat
redhatnetwork-observability/network-observability-console-plugin-rhel9:17785104612026-05-13redhat
redhatopenshift-service-mesh/kiali-rhel9:17781639092026-05-12redhat
redhatopenshift-service-mesh/kiali-rhel9:17781639862026-05-12redhat
redhatopenshift-service-mesh/kiali-rhel9:17781642082026-05-12redhat
redhatopenshift-service-mesh/kiali-rhel8:17781913782026-05-12redhat
redhatopenshift-service-mesh/kiali-rhel9:17781640422026-05-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
axios0.31.1

Weakness Classification(2)

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

Additional Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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.

Showing the most recent 100 of 118 total refreshes for this CVE.

  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:15 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-06-30 23:22 UTCEPSS rescore
  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
Show 75 more
  1. 2026-06-19 19:25 UTCEPSS rescore
  2. 2026-06-18 17:52 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-17 17:53 UTCEPSS rescore
  5. 2026-06-16 17:52 UTCEPSS rescore
  6. 2026-06-15 17:49 UTCEPSS rescore
  7. 2026-06-15 01:52 UTCEG score recompute
  8. 2026-06-15 01:52 UTCVendor advisory
  9. 2026-06-14 11:37 UTCEG score recompute
  10. 2026-06-14 11:37 UTCVendor advisory
  11. 2026-06-13 23:00 UTCEPSS rescore
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-12 01:50 UTCEG score recompute
  15. 2026-06-12 01:50 UTCVendor advisory
  16. 2026-06-11 14:00 UTCEPSS rescore
  17. 2026-06-11 13:31 UTCEG score recompute
  18. 2026-06-11 13:31 UTCVendor advisory
  19. 2026-06-10 22:18 UTCEPSS rescore
  20. 2026-06-10 13:23 UTCEG score recompute
  21. 2026-06-10 13:23 UTCVendor advisory
  22. 2026-06-10 13:22 UTCEPSS rescore
  23. 2026-06-10 13:22 UTCEPSS rescore
  24. 2026-06-10 01:05 UTCEG score recompute
  25. 2026-06-10 01:05 UTCVendor advisory
  26. 2026-06-09 12:48 UTCEG score recompute
  27. 2026-06-09 12:48 UTCVendor advisory
  28. 2026-06-09 00:31 UTCEG score recompute
  29. 2026-06-09 00:31 UTCVendor advisory
  30. 2026-06-08 14:17 UTCEPSS rescore
  31. 2026-06-08 14:17 UTCEPSS rescore
  32. 2026-06-08 06:12 UTCEG score recompute
  33. 2026-06-08 06:12 UTCVendor advisory
  34. 2026-06-07 17:54 UTCEG score recompute
  35. 2026-06-07 17:54 UTCVendor advisory
  36. 2026-06-07 15:25 UTCEPSS rescore
  37. 2026-06-07 15:25 UTCEPSS rescore
  38. 2026-06-07 05:37 UTCEG score recompute
  39. 2026-06-07 05:37 UTCVendor advisory
  40. 2026-06-06 17:19 UTCEG score recompute
  41. 2026-06-06 17:19 UTCVendor advisory
  42. 2026-06-06 13:47 UTCEPSS rescore
  43. 2026-06-06 13:47 UTCEPSS rescore
  44. 2026-06-06 04:11 UTCEG score recompute
  45. 2026-06-06 04:11 UTCVendor advisory
  46. 2026-06-05 22:47 UTCEPSS rescore
  47. 2026-06-05 15:49 UTCEG score recompute
  48. 2026-06-05 15:49 UTCVendor advisory
  49. 2026-06-05 06:10 UTCEPSS rescore
  50. 2026-06-05 06:10 UTCEPSS rescore
  51. 2026-06-05 03:31 UTCEG score recompute
  52. 2026-06-05 03:31 UTCVendor advisory
  53. 2026-06-04 15:11 UTCEG score recompute
  54. 2026-06-04 15:11 UTCVendor advisory
  55. 2026-06-04 13:12 UTCEPSS rescore
  56. 2026-06-04 13:12 UTCEPSS rescore
  57. 2026-06-04 02:53 UTCEG score recompute
  58. 2026-06-04 02:53 UTCVendor advisory
  59. 2026-06-03 14:30 UTCEG score recompute
  60. 2026-06-03 14:30 UTCVendor advisory
  61. 2026-06-03 02:09 UTCEG score recompute
  62. 2026-06-03 02:09 UTCVendor advisory
  63. 2026-06-02 13:46 UTCEG score recompute
  64. 2026-06-02 13:46 UTCVendor advisory
  65. 2026-06-02 01:28 UTCEG score recompute
  66. 2026-06-02 01:28 UTCVendor advisory
  67. 2026-06-01 13:52 UTCEPSS rescore
  68. 2026-06-01 13:52 UTCEPSS rescore
  69. 2026-06-01 13:10 UTCEG score recompute
  70. 2026-06-01 13:10 UTCVendor advisory
  71. 2026-05-31 22:30 UTCEPSS rescore
  72. 2026-05-31 22:30 UTCEPSS rescore
  73. 2026-05-31 00:16 UTCEPSS rescore
  74. 2026-05-31 00:16 UTCEPSS rescore
  75. 2026-05-31 00:16 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-42033?
CVE-2026-42033 is a high vulnerability published on April 24, 2026. Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, when Object.prototype has been polluted by any co-dependency with keys that axios reads without a hasOwnProperty guard, an attacker can (a) silently intercept and modify every JSON response before the…
When was CVE-2026-42033 disclosed?
CVE-2026-42033 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42033 actively exploited?
CVE-2026-42033 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 53.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42033?
CVE-2026-42033 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-42033?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42033, 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-42033

Explore →

Is Your Infrastructure Affected by CVE-2026-42033?

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