-
Type:
Public Security Vulnerability
-
Resolution: Fixed
-
Priority:
Highest
-
Affects Version/s: 9.4.0, 9.4.1, 9.2.4, 9.2.5, 9.2.6, 9.5.1, 9.5.2, 9.5.3, 9.2.7, 10.1.0, 9.2.8, 9.5.4, 9.2.9, 10.1.1, 10.2.0, 9.2.10, 10.1.2, 9.2.11, 9.2.12, 10.2.1, 9.2.13, 10.2.2, 9.2.14, 10.2.3, 9.2.15, 10.2.6, 9.2.17, 10.2.7, 9.2.19, 10.2.10, 10.2.11, 9.2.20, 9.2.21, 10.2.13, 10.2.14, 9.2.22, 10.2.15, 9.2.23, 9.2.24, 10.2.17, 9.2.25, 10.2.18, 9.2.26
-
Component/s: None
-
9.1
-
Critical
-
CVE-2026-71290
-
Atlassian (Internal)
-
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
-
BASM (Broken Authentication & Session Management)
-
Confluence Data Center
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 BASM (Broken Authentication & Session Management) vulnerability known as CVE-2026-71290 was introduced in versions 9.2.4, 9.4.0, 9.5.1, 10.1.0, and 10.2.0 of Confluence Data Center.
This BASM (Broken Authentication & Session Management) vulnerability, with a CVSS Score of 9.1 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N allows an unauthenticated attacker to perform actions as another user which has high impact to confidentiality, high impact to integrity, no 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.27
- Confluence Data Center 10.2: Upgrade to a release greater than or equal to 10.2.19
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: Improper TLS hostname verification vulnerability in Apache HttpComponents Client 5.4 or newer. HostnameVerificationPolicy#BUILTIN setting has no effect when used with the async version of HttpClient. An attacker that can intercept and modify traffic between the client and the server can impersonate the server by presenting a valid certificate for a different domain.
Please note the classic version of HttpClient is not affected by this vulnerability.
Affected users are recommended to upgrade to at least version 5.6.4, which fixes the issue.