CVE-2025-62718

CRITICALNVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 79% 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
9.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.9Exploit: 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.0 and 0.31.0, Axios does not correctly handle hostname normalization when checking NO_PROXY rules. Requests to loopback addresses like localhost. (with a trailing dot) or [::1] (IPv6 literal) skip NO_PROXY matching and go through the configured proxy. This goes against what developers expect and lets attackers force requests through a proxy, even if NO_PROXY is set up to protect loopback or internal services. This issue leads to the possibility of proxy bypass and SSRF vulnerabilities allowing attackers to reach sensitive loopback or internal services despite the configured protections. This vulnerability is fixed in 1.15.0 and 0.31.0.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
—
EPSS
63.9%
KEV
Not listed

Published

April 9, 2026

Last Modified

July 21, 2026

Advisory Details (10)

Auto-updated Jul 21, 2026
🔬 Proof of concept available. Patch available. Sources: github, redhat, github_commit, github_pr, github_release.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:10175
github Patch Available🟡 PoC Available

NO_PROXY Hostname Normalization Bypass Leads to SSRF · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-3p68-rc4w-qgx5
github_release Patch Available

v1.15.0

Patch available: axios/axios v1.15.0

https://github.com/axios/axios/releases/tag/v1.15.0
github_release Patch Available

v0.31.0

Patch available: axios/axios v0.31.0

https://github.com/axios/axios/releases/tag/v0.31.0
github_pr Patch Available

fix: backport the fixes from the v1 branch

Patch available: axios/axios v0.31.0 (PR #10688 merged 2026-04-11)

https://github.com/axios/axios/pull/10688
github_pr Patch Available

fix: no_proxy hostname normalization bypass leads to ssrf

Patch available: axios/axios v1.15.0 (PR #10661 merged 2026-04-06)

https://github.com/axios/axios/pull/10661
github_commit Patch Available

commit fb3befb6daac (axios/axios)

Patch available: axios/axios v1.15.0 (contains commit fb3befb6daac)

https://github.com/axios/axios/commit/fb3befb6daac6cad26b2e54094d0f2d9e47f24df
github_commit Patch Available

commit 03cdfc99e8db (axios/axios)

Patch available: axios/axios v0.31.0 (contains commit 03cdfc99e8db)

https://github.com/axios/axios/commit/03cdfc99e8db32a390e12128208b6778492cee9c
generic

RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax

https://datatracker.ietf.org/doc/html/rfc3986#section-3.2.2
generic

RFC 1034 - Domain names - concepts and facilities

https://datatracker.ietf.org/doc/html/rfc1034#section-3.1

Vendor Advisories for CVE-2025-62718(20)

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

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-mod-arch-model-registry-rhel9:17804671472026-06-10redhat
redhatautomation-gateway-0:2.5.20260422-3.el9ap2026-06-09redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17797849042026-06-09redhat
redhatquay/quay-rhel8:17808913952026-06-09redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17800829492026-06-09redhat
redhatrhtas/rhtas-console-ui-rhel9:17799715062026-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
redhatadvanced-cluster-security/rhacs-main-rhel8:17793715942026-05-26redhat
redhatquay/quay-rhel8:17796893922026-05-26redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17792930132026-05-26redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17786669872026-05-20redhat
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
redhatdiscovery/discovery-ui-rhel9:17781567562026-05-07redhat
redhatrhdh/rhdh-hub-rhel9:17779032622026-05-05redhat
redhataxios2026-05-04redhat
redhatdevspaces/dashboard-rhel9:17767955112026-04-23redhat
redhatrhdh/rhdh-hub-rhel9:17767842862026-04-22redhat
redhatopenshift-service-mesh/kiali-rhel9:17761512702026-04-16redhat
redhatopenshift-service-mesh/kiali-rhel9:17761512772026-04-16redhat
redhatopenshift-service-mesh/kiali-rhel9:17761512722026-04-16redhat
redhatopenshift-service-mesh/kiali-rhel9:17761496822026-04-16redhat
redhatopenshift-service-mesh/kiali-rhel8:17761913022026-04-16redhat

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.31.0—

Weakness Classification(3)

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

Additional Vendor Advisories

(9)

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 10× in last 7d / 46× 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 143 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-62718?
CVE-2025-62718 is a critical vulnerability published on April 9, 2026. Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.0 and 0.31.0, Axios does not correctly handle hostname normalization when checking NOPROXY rules. Requests to loopback addresses like localhost. (with a trailing dot) or [::1] (IPv6 literal) skip NOPROXY matching and go…
When was CVE-2025-62718 disclosed?
CVE-2025-62718 was first published in the National Vulnerability Database on April 9, 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-2025-62718 actively exploited?
CVE-2025-62718 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 63.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-62718?
CVE-2025-62718 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2025-62718?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-62718, 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-2025-62718

Explore →

Is Your Infrastructure Affected by CVE-2025-62718?

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

Start Free Scan →Browse All CVEs