{"answers":{"affected":"4 open source packages ship an affected version, including axios. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62718 exists.","fix":"Upgrade axios to a fixed version for your release line: 0.31.0 or 1.15.0.","what":"CVE-2025-62718 is a medium-severity server-side request forgery vulnerability in axios, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-62718 and fix it if it is affected.\n\nWhat it is: CVE-2025-62718 is a medium-severity server-side request forgery vulnerability in axios, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62718 exists.\n\nAffected packages and fixed versions:\n- axios (npm): affected all versions; fixed in 0.31.0\n- axios (npm): affected all versions; fixed in 0.31.0\n- axios (npm): affected from 1.0.0; fixed in 1.15.0\n- axios (npm): affected from 1.0.0; fixed in 1.15.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-62718/ (Markdown: https://insights.sbomify.com/CVE-2025-62718/index.md)","id":"CVE-2025-62718","markdown":"https://insights.sbomify.com/CVE-2025-62718/index.md","name":"CVE-2025-62718","record":{"aliases":["CLEANSTART-2026-FC62060","CLEANSTART-2026-PQ32851","DEBIAN-CVE-2025-62718","ECHO-eb65-3dc1-4753","GHSA-3p68-rc4w-qgx5","MINI-2334-99r5-4q39","MINI-33fj-pqqw-8c2w","MINI-5hc8-xcr5-9267","MINI-5hvh-gxx9-rp6q","MINI-6fw9-hv3h-9wpp","MINI-7wvg-j4gh-rqj9","MINI-867m-7jxm-p9vr","MINI-9r35-c8pj-7r36","MINI-c62v-v9wq-4cg9","MINI-f5pr-4gg6-j427","MINI-f642-5crf-9x6q","MINI-g969-q7cp-q265","MINI-h6ph-mhw5-hmmg","MINI-mvr7-g34g-cr89","MINI-mwjq-jx56-g99q","MINI-pff8-73c7-x2hf","MINI-v794-fjww-447v","MINI-v8c6-r58g-53hq","MINI-xq8p-f79c-42g7","ROOT-APP-NPM-CVE-2025-62718","UBUNTU-CVE-2025-62718"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Node.js HTTP client","requires_auth":"none","summary":"Attackers can bypass NO_PROXY rules via hostname normalization flaws to access internal services through a proxy, requiring an upgrade to Axios.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"axios","vendor":"axios"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-1289","name":"Improper Validation of Unsafe Equivalence in Input"},{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-441","name":"Unintended Proxy or Intermediary"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF","id":"CVE-2025-62718","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":4,"n_references":9,"next":{"headline":"LinkAce: Limited Server-Side Request Forgery (SSRF) in Keyword Fetching Functionality","id":"CVE-2025-62719"},"packages":[{"ecosystem":"npm","fixed":["0.31.0"],"introduced":["0"],"last_affected":[],"package":"axios","purl":null,"source":"GHSA-3p68-rc4w-qgx5"},{"ecosystem":"npm","fixed":["0.31.0"],"introduced":["0"],"last_affected":[],"package":"axios","purl":"pkg:npm/axios","source":"GHSA-3p68-rc4w-qgx5"},{"ecosystem":"npm","fixed":["1.15.0"],"introduced":["1.0.0"],"last_affected":[],"package":"axios","purl":null,"source":"GHSA-3p68-rc4w-qgx5"},{"ecosystem":"npm","fixed":["1.15.0"],"introduced":["1.0.0"],"last_affected":[],"package":"axios","purl":"pkg:npm/axios","source":"GHSA-3p68-rc4w-qgx5"}],"prev":{"headline":"Emlog Pro session verification code error due to clearing logic error","id":"CVE-2025-62717"},"products":["axios"],"published":"2026-04-09","related":[{"cvss_score":8.7,"headline":"Axios: Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`","id":"CVE-2026-44494","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":8.6,"headline":"axios's shouldBypassProxy does not recognize IPv4-mapped IPv6 addresses, allowing NO_PROXY bypass (incomplete fix for CVE-2025-62718)","id":"CVE-2026-44492","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":8.3,"headline":"axios before 0.33.0 Prototype Pollution via Node HTTP adapter","id":"CVE-2026-67320","kev_date_added":null,"published":"2026-08-01"},{"cvss_score":8.2,"headline":"Axios: Proxy-Authorization Credential Leak to Origin Server Across HTTP-to-HTTPS Redirect in Axios Node.js HTTP Adapter","id":"CVE-2026-44487","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":7.7,"headline":"Possible SSRF and Credential Leakage via Absolute URL in axios Requests","id":"CVE-2025-27152","kev_date_added":null,"published":"2025-03-07"},{"cvss_score":7.5,"headline":"Axios: Proxy-Authorization header leaks to redirect target when proxy is re-evaluated to direct connection","id":"CVE-2026-44486","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":7.5,"headline":"Axios: Allocation of Resources Without Limits or Throttling in axios","id":"CVE-2026-44488","kev_date_added":null,"published":"2026-06-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-10","vendors":["axios"]},"summary":"Attackers can bypass NO_PROXY rules via hostname normalization flaws to access internal services through a proxy, requiring an upgrade to Axios.","url":"https://insights.sbomify.com/CVE-2025-62718/"}