Microsoft Confluence SAML SSO Plugin/JIRA SAML SSO Plugin prior 1.3.3 incorrect implementation of authentication algorithm
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Microsoft Confluence SAML SSO Plugin and JIRA SAML SSO Plugin and classified as critical. Affected is an unknown function. Performing a manipulation results in incorrect implementation of authentication algorithm. This vulnerability is cataloged as CVE-2026-41103. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Microsoft Confluence SAML SSO Plugin and JIRA SAML SSO Plugin. It has been classified as critical. This affects an unknown part. The manipulation with an unknown input leads to a incorrect implementation of authentication algorithm vulnerability. CWE is classifying the issue as CWE-303. The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Incorrect implementation of authentication algorithm in Microsoft SSO Plugin for Jira & Confluence allows an unauthorized attacker to elevate privileges over a network.
The weakness was shared 05/12/2026 as confirmed security update guide (Website). It is possible to read the advisory at msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2026-41103. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/24/2026).
Upgrading to version 1.3.3 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-29689). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 7.8
VulDB Base Score: 7.3
VulDB Temp Score: 6.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 9.1
Vendor Vector (Microsoft): 🔒
CNA Base Score: 9.1
CNA Vector (Microsoft): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Incorrect implementation of authentication algorithmCWE: CWE-303
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Unproven
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Upgrade: Confluence SAML SSO Plugin/JIRA SAML SSO Plugin 1.3.3
Timeline
05/12/2026 VulDB entry created05/12/2026 Advisory disclosed
05/12/2026 Countermeasure disclosed
05/24/2026 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-41103 (🔒)
GCVE (CVE): GCVE-0-2026-41103
GCVE (VulDB): GCVE-100-363219
EUVD: 🔒
Entry
Created: 05/12/2026 20:03Updated: 05/24/2026 03:41
Changes: 05/12/2026 20:03 (19), 05/12/2026 20:04 (14), 05/12/2026 20:07 (35), 05/19/2026 07:42 (12), 05/24/2026 03:41 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.