CVE-2025-62718: Axios Axios Has A NO_PROXY Hostname Vulnerability

Q: What is CVE-2025-62718?

CVE-2025-62718 is a security vulnerability in Axios involving Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF under CWE-441: Unintended Proxy or Intermediary ('Confused Deputy').

Q: Which Axios versions are affected?

Affected versions include releases prior to 1.15.0, 0.31.0 across affected packages: axios.

Q: What version fixes CVE-2025-62718?

Upgrading to 1.15.0, 0.31.0 (or the latest patched release for your respective branch) resolves the vulnerability.

Q: Is axios affected?

Yes, axios is affected in releases prior to 1.15.0, 0.31.0. Upgrade your dependency to 1.15.0, 0.31.0 or later.

Q: What is the CVSS score of CVE-2025-62718?

CVE-2025-62718 has a CVSS v3.1 base score of 4.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N.

Q: What CWE is associated with CVE-2025-62718?

CVE-2025-62718 is classified under CWE-441: Unintended Proxy or Intermediary ('Confused Deputy') (The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.).

Q: How can I check npm dependencies for CVE-2025-62718?

Run the dependency tree command: 'npm ls axios'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.

MODERATE

Advisory Identifier: GHSA-3p68-rc4w-qgx5

CVSS 4.8

CWE-441 CWE-918

Published 2026-04-09

Advisory Summary

CVE-2025-62718 is a MODERATE (CVSS 4.8) axios has a no_proxy hostname vulnerability (CWE-441: Unintended Proxy or Intermediary ('Confused Deputy')) affecting Axios libraries in the npm ecosystem. The issue involves axios has a no_proxy hostname normalization bypass that leads to ssrf. Remediation is available by upgrading affected packages to version 1.15.0, 0.31.0.

CVE-2025-62718 at a Glance

CVE Identifier CVE-2025-62718

GHSA Identifier GHSA-3p68-rc4w-qgx5

Severity MODERATE

CVSS v3.1 Base Score 4.8

CWE Classification CWE-441: Unintended Proxy or Intermediary ('Confused Deputy')

Affected Product Axios

Package Ecosystem npm

Published Date 2026-04-09

Last Updated 2026-05-08

Security Impact

CVSS: 4.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)

Attack Complexity High (AC:H)

Privileges Required None (PR:N)

User Interaction None (UI:N)

Scope Unchanged (S:U)

Confidentiality Low (C:L)

Integrity Low (I:L)

Availability None (A:N)

How to Fix CVE-2025-62718

To remediate this vulnerability, upgrade all affected Axios dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

axios fixed: 1.15.0

npm install axios@1.15.0

axios fixed: 0.31.0

npm install axios@0.31.0

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls axios

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-62718, inspect your project dependencies using npm:

npm ls axios

Analyze the terminal output to locate any version of Axios in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.15.0), your application is affected.

Note: The npm ls axios command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & RFC 5280 Specification

Under RFC 5280 specifications for X.509 certificates, the Name Constraints extension defines a namespace within which all subsequent subject names in a certification path must be located. Constraints apply to various name forms including directory names, IP addresses, rfc822Name (email addresses), and uniformResourceIdentifier (URI) entries. Specifically, during certificate path validation, affected versions of Axios failed to properly normalize or enforce boundary checks when domain names contained trailing dot (.) characters. Because domain names with a trailing dot signify fully qualified domain names (FQDNs), this omission allowed non-conforming certificates to be improperly validated as compliant with the defined name constraints.

Source Advisory Statement

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. According to [RFC 1034 §3.1](https://datatracker.ietf.org/doc/html/rfc1034#section-3.1) and [RFC 3986 §3.2.2](https://datatracker.ietf.org/doc/html/rfc3986#section-3.2.2), a hostname can have a trailing dot to show it is a fully qualified domain name (FQDN). At the DNS level, `localhost.` is the same as `localhost`. However, Axios does a literal string comparison instead of normalizing hostnames before checking `NO_PROXY`. This causes requests like `http://localhost.:8080/` and `http://[::1]:8080/` to be incorrectly proxied. 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. --- **PoC** ```js import http from "http"; import axios from "axios"; const proxyPort = 5300; http.createServer((req, res) => { console.log("[PROXY] Got:", req.method, req.url, "Host:", req.headers.host); res.writeHead(200, { "Content-Type": "text/plain" }); res.end("proxied"); }).listen(proxyPort, () => console.log("Proxy", proxyPort)); process.env.HTTP_PROXY = `http://127.0.0.1:${proxyPort}`; process.env.NO_PROXY = "localhost,127.0.0.1,::1"; async function test(url) { try { await axios.get(url, { timeout: 2000 }); } catch {} } setTimeout(async () => { console.log("\n[*] Testing http://localhost.:8080/"); await test("http://localhost.:8080/"); // goes through proxy console.log("\n[*] Testing http://[::1]:8080/"); await test("http://[::1]:8080/"); // goes through proxy }, 500); ``` **Expected:** Requests bypass the proxy (direct to loopback). **Actual:** Proxy logs requests for `localhost.` and `[::1]`. --- **Impact** * Applications that rely on `NO_PROXY=localhost,127.0.0.1,::1` for protecting loopback/internal access are vulnerable. * Attackers controlling request URLs can: * Force Axios to send local traffic through an attacker-controlled proxy. * Bypass SSRF mitigations relying on NO\_PROXY rules. * Potentially exfiltrate sensitive responses from internal services via the proxy. --- **Affected Versions** * Confirmed on Axios **1.12.2** (latest at time of testing). * affects all versions that rely on Axios’ current `NO_PROXY` evaluation. --- **Remediation** Axios should normalize hostnames before evaluating `NO_PROXY`, including: * Strip trailing dots from hostnames (per RFC 3986). * Normalize IPv6 literals by removing brackets for matching.

CVE-2025-62718 Affected Axios Versions

2 component(s)

Fixed Versions:

1.15.00.31.0

Product / Package	Ecosystem	Affected Versions	Fixed Version
axios npm/axios	npm	≥ 1.0.0 < 1.15.0	1.15.0
axios npm/axios	npm	< 0.31.0	0.31.0

References

GitHub Advisory / Wiki ADVISORY

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

NVD — CVE-2025-62718 NVD

https://nvd.nist.gov/vuln/detail/CVE-2025-62718

Axios Source Repository REPOSITORY

https://github.com/axios/axios/pull/10661

Axios Source Repository REPOSITORY

https://github.com/axios/axios/pull/10688

Security Fix Commit FIX COMMIT

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

Security Fix Commit FIX COMMIT

https://github.com/axios/axios/commit/fb3befb6daac6cad26b2e54094d0f2d9e47f24df

datatracker.ietf.org/doc/html/rfc1034 WEB

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

datatracker.ietf.org/doc/html/rfc3986 WEB

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

Axios Source Repository REPOSITORY

https://github.com/axios/axios

Axios Release RELEASE

https://github.com/axios/axios/releases/tag/v0.31.0

Axios Release RELEASE

https://github.com/axios/axios/releases/tag/v1.15.0

Frequently Asked Questions

What is CVE-2025-62718?

CVE-2025-62718 is a security vulnerability in Axios involving Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF under CWE-441: Unintended Proxy or Intermediary ('Confused Deputy').

Which Axios versions are affected?

Affected versions include releases prior to 1.15.0, 0.31.0 across affected packages: axios.

What version fixes CVE-2025-62718?

Upgrading to 1.15.0, 0.31.0 (or the latest patched release for your respective branch) resolves the vulnerability.

Is axios affected?

Yes, axios is affected in releases prior to 1.15.0, 0.31.0. Upgrade your dependency to 1.15.0, 0.31.0 or later.

What is the CVSS score of CVE-2025-62718?

CVE-2025-62718 has a CVSS v3.1 base score of 4.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N.

What CWE is associated with CVE-2025-62718?

CVE-2025-62718 is classified under CWE-441: Unintended Proxy or Intermediary ('Confused Deputy') (The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.).

How can I check npm dependencies for CVE-2025-62718?

Run the dependency tree command: 'npm ls axios'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.

Machine-readable OSV JSON OSV v1.5 Schema

Normalized schema output

View Raw JSON

{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3p68-rc4w-qgx5",
  "modified" : "2026-05-08T13:46:43Z",
  "published" : "2026-04-09T17:32:19Z",
  "aliases" : [ "CVE-2025-62718" ],
  "summary" : "Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF",
  "details" : "Axios does not correctly handle hostname normalization when checking `NO_PROXY` rules.\nRequests to loopback addresses like `localhost.` (with a trailing dot) or `[::1]` (IPv6 literal) skip `NO_PROXY` matching and go through the configured proxy.\n\nThis 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.\n\nAccording to [RFC 1034 §3.1](https://datatracker.ietf.org/doc/html/rfc1034#section-3.1) and [RFC 3986 §3.2.2](https://datatracker.ietf.org/doc/html/rfc3986#section-3.2.2), a hostname can have a trailing dot to show it is a fully qualified domain name (FQDN). At the DNS level, `localhost.` is the same as `localhost`. \nHowever, Axios does a literal string comparison instead of normalizing hostnames before checking `NO_PROXY`. This causes requests like `http://localhost.:8080/` and `http://[::1]:8080/` to be incorrectly proxied.\n\nThis issue leads to the possibility of proxy bypass and SSRF vulnerabilities allowing attackers to reach sensitive loopback or internal services despite the configured protections.\n\n---\n\n**PoC**\n\n```js\nimport http from \"http\";\nimport axios from \"axios\";\n\nconst proxyPort = 5300;\n\nhttp.createServer((req, res) => {\n  console.log(\"[PROXY] Got:\", req.method, req.url, \"Host:\", req.headers.host);\n  res.writeHead(200, { \"Content-Type\": \"text/plain\" });\n  res.end(\"proxied\");\n}).listen(proxyPort, () => console.log(\"Proxy\", proxyPort));\n\nprocess.env.HTTP_PROXY = `http://127.0.0.1:${proxyPort}`;\nprocess.env.NO_PROXY = \"localhost,127.0.0.1,::1\";\n\nasync function test(url) {\n  try {\n    await axios.get(url, { timeout: 2000 });\n  } catch {}\n}\n\nsetTimeout(async () => {\n  console.log(\"\\n[*] Testing http://localhost.:8080/\");\n  await test(\"http://localhost.:8080/\"); // goes through proxy\n\n  console.log(\"\\n[*] Testing http://[::1]:8080/\");\n  await test(\"http://[::1]:8080/\"); // goes through proxy\n}, 500);\n```\n\n**Expected:** Requests bypass the proxy (direct to loopback).\n**Actual:** Proxy logs requests for `localhost.` and `[::1]`.\n\n---\n\n**Impact**\n\n* Applications that rely on `NO_PROXY=localhost,127.0.0.1,::1` for protecting loopback/internal access are vulnerable.\n* Attackers controlling request URLs can:\n\n  * Force Axios to send local traffic through an attacker-controlled proxy.\n  * Bypass SSRF mitigations relying on NO\\_PROXY rules.\n  * Potentially exfiltrate sensitive responses from internal services via the proxy.\n  \n  \n---\n\n**Affected Versions**\n\n* Confirmed on Axios **1.12.2** (latest at time of testing).\n* affects all versions that rely on Axios’ current `NO_PROXY` evaluation.\n\n---\n\n**Remediation**\nAxios should normalize hostnames before evaluating `NO_PROXY`, including:\n\n* Strip trailing dots from hostnames (per RFC 3986).\n* Normalize IPv6 literals by removing brackets for matching.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "axios"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.0"
      }, {
        "fixed" : "1.15.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "axios"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.31.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/axios/axios/security/advisories/GHSA-3p68-rc4w-qgx5"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-62718"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/axios/axios/pull/10661"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/axios/axios/pull/10688"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/axios/axios/commit/03cdfc99e8db32a390e12128208b6778492cee9c"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/axios/axios/commit/fb3befb6daac6cad26b2e54094d0f2d9e47f24df"
  }, {
    "type" : "WEB",
    "url" : "https://datatracker.ietf.org/doc/html/rfc1034#section-3.1"
  }, {
    "type" : "WEB",
    "url" : "https://datatracker.ietf.org/doc/html/rfc3986#section-3.2.2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/axios/axios"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/axios/axios/releases/tag/v0.31.0"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/axios/axios/releases/tag/v1.15.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-441", "CWE-918" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-09T17:32:19Z",
    "nvd_published_at" : "2026-04-09T15:16:08Z"
  }
}

CVSS V3

4.8 MODERATE

Attack Vector Network (AV:N)

Attack Complexity High (AC:H)

Privileges Required None (PR:N)

User Interaction None (UI:N)

Scope Unchanged (S:U)

Confidentiality Low (C:L)

Integrity Low (I:L)

Availability None (A:N)

Vector String

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Advisory Metadata

Source ID: GHSA-3p68-rc4w-qgx5
Schema Version: 1.4.0
Published: 2026-04-09 17:32
Last Modified: 2026-05-08 13:46
Database Record File: advisories/github-reviewed/2026/04/GHSA-3p68-rc4w-qgx5/GHSA-3p68-rc4w-qgx5.json