-
Type:
Public Security Vulnerability
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 10.1.0, 10.2.0, 11.0.0, 10.2.1, 10.2.2, 10.2.3, 12.0.0, 10.2.4, 11.0.1, 10.2.5, 11.0.2, 11.0.3, 10.2.6, 10.2.7, 11.0.4, 12.1.0, 10.2.8, 11.0.5, 10.2.9, 11.0.7, 11.0.8, 10.2.10, 10.2.11, 12.0.1, 12.0.2, 10.2.12, 12.1.1, 10.2.13, 10.2.14, 10.2.15, 12.1.2, 12.1.3, 10.2.16, 10.2.18, 11.1.0, 12.1.6, 12.1.7, 10.2.19, 12.1.8, 10.2.17, 10.2.20, 10.2.21, 12.1.9, 12.1.10, 10.2.22, 12.1.4, 12.1.5
-
Component/s: None
-
8.1
-
High
-
CVE-2026-65183
-
Atlassian (Internal)
-
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
-
Race condition
-
Bamboo Data Center
This High severity Race condition vulnerability was introduced in versions 10.1.0, 10.2.0, 11.0.0, 12.0.0, and 12.1.0 of Bamboo Data Center.
This Race condition vulnerability, with a CVSS Score of 8.1 and a CVSS Vector of CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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, high impact to integrity, high impact to availability, and requires no user interaction.
Atlassian recommends that Bamboo 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:
- Bamboo Data Center 10.2: Upgrade to a release greater than or equal to 10.2.23
- Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.11
See the release notes (https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html). You can download the latest version of Bamboo Data Center from the download center (https://www.atlassian.com/software/bamboo/download-archives).
The National Vulnerability Database provides the following description for this vulnerability: Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Apache Tomcat when creating unix domain sockets allows an unauthorised local user to access the unix domain socket.
This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.42 through 9.0.120.
Users are recommended to upgrade to version 11.0.25, 10.1.58, 9.0.121, which fixes the issue.