Reference page — cumulative record through Sunday, October 4, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2025-62718

CVE-2025-62718MEDIUM

Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF

  AV  AC  AT  PR  UI  VC  VI  VA   CVSS    EPSS   %ile   KEV
   N   L   P   N   N   L   L   N    6.3   .0119   66.8     —

AFFECTED
  Product  Versions              Fixed
  axios    >= 1.0.0, < 1.15.0 –  —

TIMELINE
  Oct 20  Reserved by GitHub_M
  Apr 9   Published (CNA: GitHub_M)
  Aug 24  EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.
  Aug 25  EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.
  Aug 31  EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.
  Sep 4   EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.
  Sep 7   EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.
  Sep 10  EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.

CWE-441, CWE-918, CWE-1289 · CNA: GitHub_M · CVSS v4.0 · 44 references · NVD status: Modified

Description

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.

Lifecycle

Complete event history — 8 events, chronological
Date	Event	Detail
October 20, 2025	Reserved	Reserved by GitHub_M
April 9, 2026	Published	Published (CNA: GitHub_M)
August 24, 2026	EXPLOIT PUBLISHED	EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.
August 25, 2026	EXPLOIT PUBLISHED	EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.
August 31, 2026	EXPLOIT PUBLISHED	EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.
September 4, 2026	EXPLOIT PUBLISHED	EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.
September 7, 2026	EXPLOIT PUBLISHED	EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.
September 10, 2026	EXPLOIT PUBLISHED	EXPLOIT PUBLISHED — CVE-2025-62718 (axios). Public exploit reference added.

Affected

Affected products and packages — 1 row
Vendor	Product / Package	Ecosystem	Version introduced	Fixed
axios	axios	—	>= 1.0.0, < 1.15.0	—

Weaknesses

CWE-441 · CWE-918 · CWE-1289

References (44)

Authoritative record: CVE-2025-62718 at cve.org

Vendors: axios

Weaknesses: CWE-441 · CWE-918 · CWE-1289

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2025-62718 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Sunday, October 4, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.