Skip to content

2026-11-18 - Security Bulletin for SAML Single Sign-On 6.16.4 and User Sync 2.19.3

Summary

This bulletin covers eight vulnerabilities in SAML Single Sign-On and User Sync for Jira, Confluence, Bitbucket and Bamboo. All of them are addressed in SAML Single Sign-On 6.16.4/6.16.4-p8 and User Sync 2.19.3/2.19.3-p8.

Advisory Release Date

2026-11-18

Affected Products

SAML Single Sign-On (SSO) for Jira
SAML Single Sign-On (SSO) for Confluence
SAML Single Sign-On (SSO) for Bitbucket
SAML Single Sign-On (SSO) for Bamboo
User Sync for Jira
User Sync for Confluence
User Sync for Bitbucket
User Sync for Bamboo

Affected Versions

SAML Single Sign-On: all versions up to and including 6.16.3/6.16.3-p8
User Sync: all versions up to and including 2.19.2/2.19.2-p8
See the table below for each entry

Fixed Version

Jira

  • SAML SSO 6.16.4 for Jira 8.3.0 up to 10.x

  • SAML SSO 6.16.4-p8 for Jira 11.0 and later

  • User Sync 2.19.3 for Jira 8.5.0 up to 10.x

  • User Sync 2.19.3-p8 for Jira 11.0 and later

Confluence

  • SAML SSO 6.16.4 for Confluence 6.13.10 up to 9.x

  • SAML SSO 6.16.4-p8 for Confluence 10.0 and later

  • User Sync 2.19.3 for Confluence 7.1.0 up to 9.x

  • User Sync 2.19.3-p8 for Confluence 10.0 and later

Bitbucket

  • SAML SSO 6.16.4 for Bitbucket 6.4.0 up to 9.x

  • SAML SSO 6.16.4-p8 for Bitbucket 10.0 and later

  • User Sync 2.19.3 for Bitbucket 6.7.0 up to 9.x

  • User Sync 2.19.3-p8 for Bitbucket 10.0 and later

Bamboo

  • SAML SSO 6.16.4 for Bamboo 8.1.1 up to 11.x

  • SAML SSO 6.16.4-p8 for Bamboo 12.0 and later

  • User Sync 2.19.3 for Bamboo 8.1.1 up to 11.x

  • User Sync 2.19.3-p8 for Bamboo 12.0 and later

Highest CVSS Score

9.2 Critical

Summary

This bulletin discloses a critical security vulnerability and seven further vulnerabilities in SAML Single Sign-On and User Sync. We were made aware of these vulnerabilities through our bug bounty program. We are not aware of any of them being exploited in the wild.

Every installation of SAML Single Sign-On before 6.16.4 for Jira, Confluence, Bitbucket or Bamboo needs to be updated to 6.16.4 or 6.16.4-p8 as soon as possible. From version 6.0.0 on, the critical authentication bypass affects the default configuration, and there is no workaround. On Jira instances without an enabled Jira Service Management, SAML SSO for Jira is affected by one further issue, which the same update fixes. Because SAML SSO bundles User Sync, this update also fixes the User Sync issues described below.

A separately installed User Sync app before 2.19.3 needs to be updated to 2.19.3 or 2.19.3-p8. This is most urgent if people have administrator rights without system administrator rights, if the "REST permission for Sync Single User" of a connector is set lower than System Administrators, or if a SCIM connector uses an IP allow-list together with reverse-proxy support.

After the update, rotate the credentials that were configured in SAML SSO and User Sync before it, and enable "Check Recipient of SAML message" for existing identity providers. For information about how to update your apps, please refer to Atlassian's documentation. The table and the sections below describe each vulnerability; the steps are listed under What You Need to Do.

Vulnerabilities

#

Summary

Products

Affected Versions

CVSS Severity

1

Authentication bypass in SAML response processing

SAML SSO

6.0.0 – 6.16.3 (SAML SSO)

9.2 Critical

2

Privilege escalation through Sync Single User via REST

SAML SSO, User Sync

6.9.0 – 6.16.3 (SAML SSO)
2.12.0 – 2.19.2 (User Sync)

8.8 High

3

Code execution by administrators

SAML SSO, User Sync

From 5.0.0 on (SAML SSO)
From 2.0.0 on (User Sync)

7.2 High

4

Credentials exposed to administrators

SAML SSO, User Sync

6.2.0 – 6.16.3 (SAML SSO)
2.6.0 – 2.19.2 (User Sync)

7.2 High

5

Denial of service by logged-in users

SAML SSO, User Sync

From 3.4.0 on (SAML SSO)
From 1.3.0 on (User Sync)

6.5 Medium

6

Login without application access on Jira without Jira Service Management

SAML SSO for Jira

All versions up to 6.16.3 (SAML SSO)

5.4 Medium

7

SCIM IP allow-list could be bypassed

SAML SSO, User Sync

6.13.0 – 6.16.3 (SAML SSO)
2.16.0 – 2.19.2 (User Sync)

4.8 Medium

8

Reset of a connector's OAuth authorization without permission

SAML SSO, User Sync

From 5.0.0 on (SAML SSO)
From 2.0.0 on (User Sync)

3.7 Low

All version ranges include the matching -p8 versions.

1. Authentication bypass in SAML response processing

Under certain conditions, an unauthenticated attacker could log in to the Atlassian application as any user, including administrators. The default configuration was affected, and there is no configuration workaround. After the upgrade, such a login is no longer possible.

CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

2. Privilege escalation through Sync Single User via REST

When the "REST permission for Sync Single User" of a User Sync connector (connector configuration, tab Support) was set to Administrators or Users instead of the default System Administrators, a caller with that lower permission could, under certain conditions, gain further privileges. An attacker needed to be a licensed user, or an administrator if the setting was Administrators, and to know the connector. After the upgrade, only system administrators can pass user data to this call, and for Just-in-Time connectors the call always requires a system administrator.

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

3. Code execution by administrators

Administrators without system administrator rights could run code on the server. An attacker needed administrator rights in the Atlassian application. After the upgrade, this requires system administrator rights.

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

4. Credentials exposed to administrators

Under certain conditions, administrators without system administrator rights could obtain credentials configured in SAML SSO or User Sync. An attacker needed administrator rights in the Atlassian application. After the upgrade, this is no longer possible. Credentials obtained before the upgrade remain valid, so rotate them as described in Step 2 below.

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

5. Denial of service by logged-in users

Under certain conditions, a logged-in user could make the application unresponsive. An attacker needed an account that can log in to the Atlassian application. After the upgrade, this requires system administrator rights.

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

6. Login without application access on Jira without Jira Service Management

On Jira instances where Jira Service Management is not installed or not enabled, an existing, active user without Jira application access could obtain a Jira session through SAML SSO. An attacker needed to log in at the identity provider with an account that matches such a Jira user. The session gave the attacker only what that user's permissions allow. After the upgrade, users without Jira application access can no longer log in this way.

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

7. SCIM IP allow-list could be bypassed

For SCIM connectors with an IP allow-list and reverse-proxy support enabled, requests from addresses outside the allow-list could be accepted under certain circumstances. An attacker needed the connector's valid SCIM bearer token and had to reach the application through the trusted reverse proxy. After the upgrade, the allow-list is enforced in these setups as well. If more than one proxy sits in front of the application, every proxy has to be listed as a trusted reverse proxy in the SCIM connector; otherwise legitimate requests are rejected.

CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

8. Reset of a connector's OAuth authorization without permission

The stored OAuth authorization of a User Sync connector could be reset by users without system administrator rights. Synchronization through a connector that uses the authorization code flow then failed until an administrator authorized it again. An attacker needed to know the connector, and the connector had to use OAuth authorization. After the upgrade, only system administrators can reset the authorization.

CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

What You Need to Do

Step 1: Update

Update SAML Single Sign-On to version 6.16.4/6.16.4-p8 or later. SAML SSO bundles User Sync, so this update also fixes the User Sync issues. If User Sync is installed as a separate app, update it to version 2.19.3/2.19.3-p8 or later. For information about how to update your apps, please refer to Atlassian's documentation.

In Case You Can't Update

There is no workaround for the authentication bypass (1). For some of the other issues, the following reduces the risk until you can update:

  • Set "REST permission for Sync Single User" back to System Administrators on every connector (2).

  • Limit administrator permissions to people you trust with system administrator rights and with the SSO and SCIM credentials (3, 4).

  • Rotate the SCIM bearer token if it may be known to others. Disabling reverse-proxy support closes the gap, but it also blocks provisioning that reaches the application through a proxy (7).

If you can't update the app, please contact us through our support portal.

Step 2: Rotate Credentials

Credentials configured in SAML SSO and User Sync before the update may be known to administrators without system administrator rights. Rotate them, for example OIDC/OAuth2 client secrets of identity providers and SCIM bearer tokens.

Step 3: Enable "Check Recipient of SAML message"

Enable "Check Recipient of SAML message" for existing identity providers. New identity providers have it enabled by default.

Step 4: Check Trusted Proxies and Connector Authorizations

If more than one proxy sits in front of the application, list every proxy as a trusted reverse proxy in each SCIM connector that uses reverse-proxy support; otherwise legitimate requests are rejected. If a connector's synchronization fails because of a missing authorization, authorize the connector again.

Step 5: Impact Analysis

Review recent logins, administrator accounts, the members of administrator groups and the audit log for unexpected user, group or configuration changes. This matters most if "REST permission for Sync Single User" was lowered on a connector or if people have administrator rights without system administrator rights; in that case also review the server for unexpected changes.

Support

If you have any questions or need assistance, please contact us through our support portal.