CVE-2025-62718

This is a vulnerability in a non-Atlassian Confluence dependency. Atlassian's application of this dependency presents a lower, non-critical assessed risk.   This Critical severity SSRF (Server-Side Request Forgery) vulnerability was introduced in versions 9.0.1, 9.1.0, 9.2.0, 9.3.1, 9.4.0, 9.5.1 10.0.2, 10.1.0 and 10.2.0 of Confluence Data Center.   This SSRF (Server-Side Request Forgery) vulnerability, with a CVSS Score of 9.9 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L allows an unauthenticated attacker to access the content of internal network resources. When running in an environment like Amazon EC2, this flaw may be used to access a metadata resource that provides access credentials and other potentially confidential information which has high impact to confidentiality, low impact to integrity, low impact to availability, and requires no user interaction.   Atlassian recommends that Confluence Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: * Confluence Data Center 9.2: Upgrade to a release greater than or equal to 9.2.22 * Confluence Data Center 10.2: Upgrade to a release greater than or equal to 10.2.14 See the release notes (https://confluence.atlassian.com/doc/confluence-release-notes-327.html). You can download the latest version of Confluence Data Center from the download center (https://www.atlassian.com/software/confluence/download-archives).   The National Vulnerability Database provides the following description for this vulnerability:   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.

EPSS 0.07% · 21.3th percentile