CVE-2026-44490

HIGHNVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
8.2EG
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.4%CVSS: 8.2Exploit: 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 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.2HIGHmedium confidence
EG Risk
53
EG Risk 53/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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 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.4%
EPSS %ILE
33rd
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 (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-18). 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: 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.

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

May 29, 2026

Last Modified

June 15, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

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

(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 (8 versions)
  • every version up to 1.16.0-1: fixed in 1.16.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
axios—
  • 1.0.0 up to 1.16.0: fixed in 1.16.0
  • every version up to 0.32.0: fixed in 0.32.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 31× 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 155 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 55 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-44490?
CVE-2026-44490 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-44490 published?
The CVE record for CVE-2026-44490 was published on May 29, 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 June 15, 2026; the record at its source may have been updated since.
Is CVE-2026-44490 actively exploited?
CVE-2026-44490 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-44490 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44490 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-44490

Explore →

Is Your Infrastructure Affected by CVE-2026-44490?

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

Book a Demo →Browse All CVEs