This High severity BASM (Broken Authentication & Session Management) vulnerability was introduced in versions 10.0.0
Source GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 11.3.13 or 10.3.27 soon.
Data as of 17 Nov 2026, 19:51 UTC
Thin evidence
One scorer or none| CNA (atlassian) | CVSS 4.0 | 8.7 |
|---|
- Patch
- Available – fixed in 11.3.13, 10.3.27
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade com.atlassian.jira/jira-servicemanagement-datacenter to 11.3.13 or 10.3.27.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AtlassianJira Service Management Data Center | Affected
| Fixed in– |
Mavencom.atlassian.jira/jira-servicemanagement-datacenterpkg:maven/com.atlassian.jira/jira-servicemanagement-datacenterOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Atlassian recommends upgrading affected Jira Service Management Data Center instances to version 10.3.27 or later for the 10.3 series, or 11.3.13 or later for the 11.3 series. Applying these official fixes fully mitigates the vulnerability. No alternative mitigations are specified.
Description
A high severity Broken Authentication and Session Management (BASM) vulnerability affects Jira Service Management Data Center versions 10.0.0 and 11.0.0. This flaw allows unauthenticated attackers to perform actions as other users, posing significant security risks. Atlassian recommends upgrading to fixed versions 10.3.27 or later for the 10.3 series, and 11.3.13 or later for the 11.3 series to remediate this issue. The vulnerability was discovered through Atlassian's Bug Bounty program.