CVE-2026-42041

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.8 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-05-05) is not newer than that change (2026-09-10), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-25606 (ENISA EUVD) · GHSA-w9j2-pvgh-6h63 (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

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, the Axios library is vulnerable to a Prototype Pollution "Gadget" attack that allows any Object.prototype pollution to silently suppress all HTTP error responses (401, 403, 500, etc.), causing them to be treated as successful responses. This completely bypasses application-level authentication and error handling. The root cause is that validateStatus is the only config property using the mergeDirectKeys merge strategy, which uses JavaScript's in operator — an operator that inherently traverses the prototype chain. When Object.prototype.validateStatus is polluted with () => true, all HTTP status codes are accepted as success. This vulnerability is fixed in 1.15.1 and 0.31.1.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 24, 2026

Last Modified

September 10, 2026

Advisory Details (10)

Auto-updated Jul 8, 2026
Patch available. Sources: github, redhat.
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:17474
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:17468
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:16874
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:16542
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:16535
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:16534
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:16532
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:16476
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:14937
GitHub advisoryMentions a patch (unverified)

Authentication Bypass via Prototype Pollution Gadget in `validateStatus` Merge Strategy · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-w9j2-pvgh-6h63

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhceph/rhceph-9-rhel10:17908435272026-10-21redhat
redhatmta/mta-ui-rhel9:17851690132026-08-04redhat
redhatrhacm2/console-rhel9:17834517292026-07-08redhat
redhatrhdh/rhdh-hub-rhel9:17827612442026-06-30redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17801051792026-06-16redhat
redhatrhdh/rhdh-hub-rhel9:17811873422026-06-16redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17810324952026-06-16redhat
redhatsatellite/iop-advisor-frontend-rhel9:17811816732026-06-16redhat
redhatmulticluster-engine/console-mce-rhel9:17809108882026-06-11redhat
redhatrhacm2/console-rhel9:17806008232026-06-11redhat
redhatrhmtc/openshift-migration-ui-rhel8:17805907172026-06-10redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17804671472026-06-10redhat
redhataxios2026-06-10redhat
redhatquay/quay-rhel8:17808913952026-06-09redhat
redhatmulticluster-engine/console-mce-rhel9:17809175312026-06-08redhat
redhatrhacm2/console-rhel9:17808767342026-06-08redhat
redhatquay/quay-rhel8:17798114732026-06-04redhat
redhatquay/quay-rhel8:17798222612026-06-03redhat
redhatquay/quay-rhel9:17799222052026-06-02redhat
redhatquay/quay-rhel8:17798114122026-06-02redhat
redhatdevspaces/dashboard-rhel9:17793412892026-05-28redhat
redhatrhdh/rhdh-hub-rhel9:17798415862026-05-27redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17793715942026-05-26redhat
redhatquay/quay-rhel8:17796893922026-05-26redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17792930132026-05-26redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17786450992026-05-20redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17785393382026-05-19redhat
redhatmulticluster-engine/console-mce-rhel9:17785326102026-05-19redhat
redhatquay/quay-rhel9:17792040862026-05-19redhat
npmaxios @ 1.15.1 (fixes >= 1.0.0, < 1.15.1)—ghsa
npmaxios @ 0.31.1 (fixes <= 0.31.0)—ghsa

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-axios0.21.1+dfsg-1 ... 1.8.4+dfsg-1 (40 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (22 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (12 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (7 versions)
  • every version up to 1.15.2-1: fixed in 1.15.2-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
axios—
  • 1.0.0 up to 1.15.1: fixed in 1.15.1
  • every version up to 0.31.1: fixed in 0.31.1
—

Weakness Classification(3)

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

Additional Vendor Advisories

(18)

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 282 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 182 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  3. 2026-11-01 07:50 UTCGHSA enrichmentGHSA-w9j2-pvgh-6h63 · GitHub severity MODERATE · GitHub CVSS 4.8
  4. 2026-11-01 07:50 UTCEG score recompute
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-30 17:55 UTCOSV refresh
  7. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  9. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  13. 2026-10-25 14:29 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  16. 2026-10-23 02:18 UTCEG score recompute
  17. 2026-10-23 02:18 UTCVendor advisory
  18. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  19. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  20. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  21. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  22. 2026-10-18 03:41 UTCEG score recompute
  23. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  24. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
Show 75 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  4. 2026-10-12 16:07 UTCEG score recompute
  5. 2026-10-11 19:49 UTCEG score recompute
  6. 2026-10-11 17:03 UTCEG score recompute
  7. 2026-10-11 14:29 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  19. 2026-09-29 20:02 UTCOSV refresh
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  22. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  26. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  27. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  28. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  29. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  30. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  31. 2026-09-10 13:40 UTCVendor advisory
  32. 2026-09-10 12:27 UTCEG score recompute
  33. 2026-09-10 12:27 UTCVendor advisory
  34. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  35. 2026-09-09 13:41 UTCVendor advisory
  36. 2026-09-09 12:39 UTCEG score recompute
  37. 2026-09-09 12:39 UTCVendor advisory
  38. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  39. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  40. 2026-09-07 13:59 UTCVendor advisory
  41. 2026-09-07 13:10 UTCEG score recompute
  42. 2026-09-07 13:10 UTCVendor advisory
  43. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  44. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  45. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  46. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  47. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  48. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  49. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  50. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  51. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  52. 2026-08-26 16:12 UTCEG score recompute
  53. 2026-08-26 16:12 UTCVendor advisory
  54. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  55. 2026-08-26 12:22 UTCEG score recompute
  56. 2026-08-26 12:22 UTCVendor advisory
  57. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  58. 2026-08-25 13:25 UTCVendor advisory
  59. 2026-08-25 12:21 UTCEG score recompute
  60. 2026-08-25 12:21 UTCVendor advisory
  61. 2026-08-24 13:31 UTCVendor advisory
  62. 2026-08-24 12:26 UTCEG score recompute
  63. 2026-08-24 12:26 UTCVendor advisory
  64. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  65. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  66. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  67. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  68. 2026-08-19 12:27 UTCVendor advisory
  69. 2026-08-19 12:11 UTCEG score recompute
  70. 2026-08-19 12:11 UTCVendor advisory
  71. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  72. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  73. 2026-08-17 12:20 UTCVendor advisory
  74. 2026-08-17 12:12 UTCEG score recompute
  75. 2026-08-17 12:12 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-42041?
CVE-2026-42041 is a medium-severity vulnerability; its CVE record was 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, the Axios library is vulnerable to a Prototype Pollution "Gadget" attack that allows any Object.prototype pollution to silently suppress all HTTP error responses (401, 403, 500, etc.), causing them to be…
When was the CVE record for CVE-2026-42041 published?
The CVE record for CVE-2026-42041 was published on April 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-42041 actively exploited?
CVE-2026-42041 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42041?
CVE-2026-42041 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-42041?
A fix for CVE-2026-42041 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42041 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-42041?

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