-
Type:
Public Security Vulnerability
-
Resolution: Fixed
-
Priority:
Highest
-
Affects Version/s: 11.0.0, 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, 10.2.19
-
Component/s: None
-
9.1
-
Critical
-
CVE-2026-101356
-
Atlassian (Internal)
-
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
-
Race condition
-
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 Race condition vulnerability known as CVE-2026-101356 was introduced in versions 9.2.21, 10.2.13, and 11.0.0 of Confluence Data Center.
This Race condition 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:N/A:H allows an unauthenticated attacker to modify code sequences in which exclusive access to shared resources is operating concurrently which has high impact to confidentiality, no impact to integrity, high 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.20
- Confluence Data Center 11.0: Upgrade to a release greater than or equal to 11.0.1
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: Incorrect object recycling and re-use vulnerability in Apache Tomcat affecting HTTP/2 processing of asynchronous servlets can trigger request and/or response mix-up between users.
This issue affects Apache Tomcat: from 11.0.22 through 11.0.26, from 10.1.55 through 10.1.60, from 9.0.118 through 9.0.122.
Users are recommended to upgrade to version 11.0.27, 10.1.61 or 9.0.123, which fixes the issue.