CVE-2026-44496

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 54% 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, secondary
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Axios is a promise based HTTP client for the browser and Node.js. Axios versions before 0.32.0 on the 0.x line and before 1.16.0 on the 1.x line build a regular expression from the configured XSRF cookie name without escaping regex metacharacters. In standard browser environments, an attacker who can influence the cookie name passed to axios can cause expensive regex backtracking while axios reads document.cookie. The practical impact is client-side availability degradation, such as freezing the affected browser tab while axios prepares a request. The issue does not affect ordinary Node.js HTTP adapter usage, React Native, or web workers, where axios does not read document.cookie. This vulnerability is fixed in 0.32.0 and 1.16.0.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
46.1%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 22, 2026

Advisory Details (1)

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

Regular Expression Denial of Service (ReDoS) via Cookie Name Injection · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-hfxv-24rg-xrqf

Vendor Advisories for CVE-2026-44496(20)

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

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmulticluster-engine/console-mce-rhel9:17833510022026-07-15redhat
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat
redhatmulticluster-engine/console-mce-rhel9:17833481812026-07-08redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17828804722026-07-08redhat
redhatrhacm2/console-rhel9:17834517292026-07-08redhat
redhatdevspaces/dashboard-rhel9:17824987922026-07-08redhat
redhatopenshift4/ose-console-rhel9:17822440202026-07-01redhat
redhatopenshift4/ose-console:17821270912026-07-01redhat
redhatquay/quay-rhel8:17824877172026-06-30redhat
redhatrhdh/rhdh-hub-rhel9:17827612442026-06-30redhat
redhatopenshift-service-mesh/kiali-rhel8:17822875802026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822018332026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822015372026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822018122026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822014662026-06-29redhat
redhatmulticluster-engine/console-mce-rhel9:17821570852026-06-28redhat
redhatrhacm2/console-rhel9:17821575142026-06-28redhat
redhatquay/quay-rhel8:17819373572026-06-25redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17816950122026-06-23redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17817319142026-06-23redhat
redhatquay/quay-rhel8:17818780702026-06-23redhat
redhatrhdh/rhdh-hub-rhel9:17811873422026-06-16redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17793715942026-05-26redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17792930132026-05-26redhat

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
axios—0.32.0—

Weakness Classification(2)

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

Additional Vendor Advisories

(17)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 57× 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-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-16 00:18 UTCVendor advisory
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-14 16:26 UTCVendor advisory
  12. 2026-07-14 03:23 UTCVendor advisory
  13. 2026-07-13 22:30 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 01:09 UTCVendor advisory
  17. 2026-07-11 12:08 UTCVendor advisory
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-08 22:45 UTCVendor advisory
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-08 09:43 UTCVendor advisory
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 02:59 UTCVendor advisory
Show 50 more
  1. 2026-07-06 02:23 UTCEPSS rescore
  2. 2026-07-05 02:30 UTCEPSS rescore
  3. 2026-07-04 06:31 UTCEPSS rescore
  4. 2026-07-03 19:18 UTCVendor advisory
  5. 2026-07-03 02:16 UTCVendor advisory
  6. 2026-07-02 12:20 UTCVendor advisory
  7. 2026-07-01 23:17 UTCVendor advisory
  8. 2026-07-01 15:07 UTCEPSS rescore
  9. 2026-07-01 09:09 UTCVendor advisory
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-30 20:06 UTCVendor advisory
  12. 2026-06-29 23:09 UTCVendor advisory
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 10:01 UTCVendor advisory
  15. 2026-06-28 19:06 UTCVendor advisory
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 06:04 UTCVendor advisory
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 17:00 UTCVendor advisory
  20. 2026-06-27 03:58 UTCVendor advisory
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 14:56 UTCVendor advisory
  23. 2026-06-26 01:20 UTCVendor advisory
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
  26. 2026-06-25 11:12 UTCVendor advisory
  27. 2026-06-24 22:10 UTCVendor advisory
  28. 2026-06-24 14:05 UTCEPSS rescore
  29. 2026-06-24 09:03 UTCVendor advisory
  30. 2026-06-23 21:33 UTCEPSS rescore
  31. 2026-06-23 18:47 UTCVendor advisory
  32. 2026-06-23 02:18 UTCVendor advisory
  33. 2026-06-22 14:25 UTCEPSS rescore
  34. 2026-06-22 14:25 UTCEPSS rescore
  35. 2026-06-21 14:56 UTCEPSS rescore
  36. 2026-06-21 14:56 UTCEPSS rescore
  37. 2026-06-21 01:59 UTCEPSS rescore
  38. 2026-06-20 12:10 UTCVendor advisory
  39. 2026-06-19 19:52 UTCVendor advisory
  40. 2026-06-19 19:25 UTCEPSS rescore
  41. 2026-06-18 21:25 UTCVendor advisory
  42. 2026-06-18 17:52 UTCEPSS rescore
  43. 2026-06-18 17:52 UTCEPSS rescore
  44. 2026-06-17 17:53 UTCEPSS rescore
  45. 2026-06-16 17:52 UTCEPSS rescore
  46. 2026-06-15 17:49 UTCEPSS rescore
  47. 2026-06-13 23:00 UTCEPSS rescore
  48. 2026-06-12 23:12 UTCEPSS rescore
  49. 2026-06-12 23:12 UTCEPSS rescore
  50. 2026-06-04 15:10 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44496?
CVE-2026-44496 is a high vulnerability published on June 4, 2026. Axios is a promise based HTTP client for the browser and Node.js. Axios versions before 0.32.0 on the 0.x line and before 1.16.0 on the 1.x line build a regular expression from the configured XSRF cookie name without escaping regex metacharacters. In standard browser environments, an attacker who…
When was CVE-2026-44496 disclosed?
CVE-2026-44496 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44496 actively exploited?
CVE-2026-44496 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44496?
CVE-2026-44496 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-44496?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44496, 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-44496

Explore →

Is Your Infrastructure Affected by CVE-2026-44496?

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

Start Free Scan →Browse All CVEs