-
Type:
Public Security Vulnerability
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 9.1.0, 9.0.1, 9.2.0, 9.3.0, 9.4.0, 9.5.0, 9.4.1, 9.4.2, 9.6.0, 9.4.3, 9.4.4, 9.4.5, 10.0.0, 9.4.6, 9.4.7, 9.4.8, 9.4.9, 9.4.11, 9.4.12, 9.4.13, 9.4.14, 9.4.15, 9.4.16, 10.1.1, 10.2.0, 9.4.17, 9.4.18, 10.2.1, 10.3.0, 9.4.19, 10.2.2, 10.2.3, 9.4.20, 10.2.4, 9.4.21, 10.3.1, 9.4.22, 10.2.5, 9.4.23
-
Component/s: None
-
7.5
-
High
-
CVE-2026-50010
-
Atlassian (Internal)
-
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
-
BASM (Broken Authentication & Session Management)
-
Bitbucket Data Center
This High severity BASM (Broken Authentication & Session Management) vulnerability known as CVE-2026-50010 was introduced in 9.0.1 and later of Bitbucket Data Center and Server.
This BASM (Broken Authentication & Session Management) vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N allows an unauthenticated attacker to perform actions as another user.
Atlassian recommends that Bitbucket Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:
- Bitbucket Data Center and Server 10.3: Upgrade to a release greater than or equal to 10.3.2
- Bitbucket Data Center and Server 10.2: Upgrade to a release greater than or equal to 10.2.6
- Bitbucket Data Center and Server 9.4: Upgrade to a release greater than or equal to 9.4.24
See the release notes (https://confluence.atlassian.com/bitbucketserver/release-notes). You can download the latest version of Bitbucket Data Center and Server from the download center (https://www.atlassian.com/software/bitbucket/download-archives).
The National Vulnerability Database provides the following description for this vulnerability: Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, SimpleTrustManagerFactory.engineGetTrustManagers() and related paths wrap any user-supplied plain X509TrustManager in X509TrustManagerWrapper, which extends X509ExtendedTrustManager but implements the 3-arg checkServerTrusted(chain, authType, SSLEngine) by discarding the SSLEngine and calling the 2-arg delegate. Because the object now IS an X509ExtendedTrustManager, neither SunJSSE's internal AbstractTrustManagerWrapper nor Netty's own OpenSslX509TrustManagerWrapper will re-wrap it to add endpoint-identification. Consequently, even though Netty 4.2 sets endpointIdentificationAlgorithm="HTTPS" by default, a client built with `SslContextBuilder.forClient().trustManager(somePlainX509TrustManager)` performs no hostname verification at all. Versions 4.1.135.Final and 4.2.15.Final patch the issue.