CVE-2025-62718

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 1.2% (67th 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-04-09) is not newer than that change (2026-10-14), 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-2025-209381 (ENISA EUVD) · GHSA-3p68-rc4w-qgx5 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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: 1.2%CVSS: 9.9Exploit: 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.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.9CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.2%
EPSS %ILE
67th
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.2% 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 9, 2026

Last Modified

October 14, 2026

Advisory Details (10)

Auto-updated Oct 30, 2026
Patch available. Sources: github_commit, github_pr, github_release, github, redhat.
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:10175
GitHub advisoryMentions a patch (unverified)

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 pull request 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 pull request 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
Web page

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

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

RFC 1034 - Domain names - concepts and facilities

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

Patch Availability(32)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatdevspaces/code-rhel9:17925993882026-10-26redhat
redhatrhceph/rhceph-9-rhel10:17908435272026-10-21redhat
redhatansible-automation-platform-26/lightspeed-rhel9-operator:17871846822026-08-24redhat
redhatrhmtc/openshift-migration-ui-rhel8:17836905322026-07-20redhat
redhatrhacm2/console-rhel9:17834517292026-07-08redhat
redhatcluster-observability-operator/monitoring-console-plugin-pf5-rhel9:17811166672026-06-15redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17804671472026-06-10redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17800829492026-06-09redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17797849042026-06-09redhat
redhatautomation-gateway-0:2.5.20260422-3.el9ap2026-06-09redhat
redhatquay/quay-rhel8:17808913952026-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:17783838632026-05-14redhat
redhatmulticluster-engine/console-mce-rhel9:17785113482026-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:17761512772026-04-16redhat
npmaxios @ 1.15.0 (fixes >= 1.0.0, < 1.15.0)—ghsa
npmaxios @ 0.31.0 (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 (41 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 (6 versions)
  • every version up to 1.15.0-1: fixed in 1.15.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
axios—
  • 1.0.0 up to 1.15.0: fixed in 1.15.0
  • every version up to 0.31.0: fixed in 0.31.0
—

Weakness Classification(3)

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

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 23× in last 7d / 81× 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 98 of 386 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 288 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-62718?
CVE-2025-62718 is a critical-severity vulnerability; its CVE record was 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 NO_PROXY rules. Requests to loopback addresses like localhost. (with a trailing dot) or [::1] (IPv6 literal) skip NO_PROXY matching and…
When was the CVE record for CVE-2025-62718 published?
The CVE record for CVE-2025-62718 was published on April 9, 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 October 14, 2026; the record at its source may have been updated since.
Is CVE-2025-62718 actively exploited?
CVE-2025-62718 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2025-62718 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-62718 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-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.