9
CVEs
1
Critical
7
High
0
KEV
0
PoC
6
Unpatched C/H
33.3%
Patch Rate
0.3%
Avg EPSS
Severity Breakdown
CRITICAL
1
HIGH
7
MEDIUM
1
LOW
0
Monthly CVE Trend
Affected Products (30)
Jira Server
88
Jira
83
Jira Data Center
44
Crucible
32
Fisheye
32
Confluence Server
31
Confluence
27
Confluence Data Center
26
Data Center
24
Jira Software Data Center
23
Java
20
Bamboo
20
Mattermost
18
Crowd
11
Bitbucket
11
Jira Service Desk
10
Jira Service Management
9
Sourcetree
8
Open Redirect
7
Xwiki
6
Mcp Atlassian
5
Agiloft
4
In App Desktop Notifications
4
Mattermost Server
4
S Notify
4
Jira Pipeline Steps
4
Pro Macros
4
Secure Login
3
Companion
3
Hipchat
3
Top Risky CVEs
| CVE | Summary | Severity | CVSS | EPSS | Priority | Signals |
|---|---|---|---|---|---|---|
| CVE-2026-21580 | Stored cross-site scripting combined with privilege escalation in Confluence Data Center and Server lets an unauthenticated attacker persist malicious HTML/JavaScript that runs in a victim's browser, enabling actions performed as a higher-privileged user and abuse of insecure default configurations. Atlassian rates it Critical (vendor CVSS 4.0 score 9.3; the advisory body text separately cites 8.6), and it affects a long list of 7.x through 10.2.x branches. There is no public exploit identified at time of analysis and it is not on CISA KEV; it was found through Atlassian's bug bounty program. | CRITICAL | 9.3 | 0.4% | 47 |
No patch
|
| CVE-2026-21582 | Broken authentication in Atlassian Crowd Data Center 7.2.1 permits a remote, unauthenticated attacker to perform actions on behalf of any other user, effectively bypassing the platform's identity and session controls. The flaw was introduced specifically in version 7.2.1, discovered through Atlassian's Penetration Testing program, and carries a CVSS 4.0 score of 8.8 with scope-changing impact that cascades to all downstream SSO-federated applications. No active exploitation (CISA KEV) and no public exploit code have been identified at time of analysis, though the cross-system propagation potential demands urgent patching. | HIGH | 8.8 | 0.4% | 44 |
No patch
|
| CVE-2026-73496 | MCP Atlassian, the Model Context Protocol server that bridges AI clients to Confluence and Jira, resolves client-supplied attachment paths on the server itself, so a remote client with write-tool access can read arbitrary files from the server host in versions before 0.22.0. The confluence_upload_attachment, confluence_upload_attachments and jira_update_issue tools all funnel an unconfined file_path into os.path.abspath() plus open(), and the resulting bytes are uploaded to Atlassian as an attachment — giving the attacker a convenient exfiltration channel for server files, environment-held Atlassian credentials, or other tenants' data. The vendor advisory includes a working proof-of-concept (publicly available exploit code exists), but no active exploitation is confirmed (no CISA KEV listing); the CVSS 3.1 score is 7.7 with EPSS not provided in the input. Only local single-user stdio deployments are outside the trust boundary. | HIGH | 7.7 | 0.3% | 38 |
|
| CVE-2026-21584 | Improper authorization in Atlassian Bamboo Data Center across six affected release lines (10.0.x through 12.1.x) enables authenticated low-privilege users to bypass access controls and reach restricted resources or functionality, with Atlassian tagging the flaw as carrying arbitrary code execution risk. The vulnerability was discovered through Atlassian's own penetration testing program and affects Data Center deployments only - not Bamboo Cloud. No public exploit code or CISA KEV listing exists at time of analysis, but the high confidentiality and integrity impact ratings (VC:H/VI:H in CVSS 4.0) and the RCE tag make this a credible escalation risk in any environment where untrusted or lightly-privileged users hold Bamboo accounts. | HIGH | 7.6 | 0.4% | 38 |
No patch
|
| CVE-2026-66908 | JWT claim validation in Apache Camel's Platform HTTP Main component silently fails to enforce issuer and audience constraints when neither jwtIssuer nor jwtAudience is configured, causing the embedded Vert.x HTTP server to accept any unexpired token signed by any key in the trusted keystore. Affected are Apache Camel versions 4.8.0 through 4.21.x across both the application server and management server paths. An attacker who possesses a valid JWT from any identity provider trusted by the configured keystore - such as a token legitimately issued for a different service in a shared IdP environment - can authenticate to the Camel HTTP endpoints without holding credentials intended for that service. No public exploit has been identified at time of analysis, and CISA KEV listing is absent. | HIGH | 7.5 | 0.3% | 38 |
|
| CVE-2026-21586 | An improper authorization flaw in Atlassian Confluence Data Center lets an authenticated, low-privileged user reach resources and functionality they should not be able to access, resulting in high confidentiality impact against the affected instance. The defect was introduced across a broad set of release trains — 7.4.0, 7.13.0, 8.5.0, 8.9.0, 9.0.1, 9.1.0, 9.2.0, 9.3.1, 9.4.0, 9.5.1, 10.0.2, 10.1.0 and 10.2.0 — meaning most currently maintained Data Center deployments built on those lines are exposed until upgraded. Atlassian rates the issue 7.1 (CVSS 4.0, AV:N/AC:L/PR:L/UI:N/VC:H) and has shipped fixes in 9.2.24 and 10.2.17; there is no evidence of public exploit code or confirmed active exploitation at time of analysis. | HIGH | 7.1 | – | 36 |
No patch
|
| CVE-2026-21587 | Improper authorization in Atlassian Jira Service Management Data Center 11.3.0 through 11.3.10 lets an authenticated, low-privileged attacker reach functionality and data they should not be able to access, with the vendor scoring it 7.1 in CVSS 4.0 (AV:N/AC:L/PR:L/UI:N/VI:H). Atlassian states the flaw was discovered through its own penetration-testing program and that the impact could extend from exposure of sensitive resources to arbitrary code execution, though the published CVSS 4.0 vector only credits a high integrity impact and rates confidentiality and availability as none. No CISA KEV listing, EPSS score, or public exploit code was provided in the source data, so at time of analysis this should be treated as a confirmed but not yet observed-in-the-wild authorization bypass; patched versions (11.3.11 and later) are already available. | HIGH | 7.1 | – | 36 |
No patch
|
| CVE-2026-21588 | Authenticated denial of service in Atlassian Confluence Data Center allows a low-privileged logged-in user to make the application unavailable to its intended users, with no confidentiality or integrity impact. The flaw was introduced across a broad swath of releases (8.9.0 through 10.2.0) and Atlassian rates it High with a CVSS 4.0 score of 7.1. Fixed builds are 9.2.24 and later on the 9.2 branch and 10.2.17 and later on the 10.2 branch; no public exploit code or confirmed active exploitation was identified at time of analysis. | HIGH | 7.1 | – | 36 |
No patch
|
| CVE-2026-73497 | Server-side request forgery in the MCP Atlassian MCP server (versions 0.17.0 through 0.21.x) allows remote unauthenticated attackers to force the server to make outbound requests to internal addresses such as the cloud metadata endpoint 169.254.169.254. The flaw is an incomplete-fix TOCTOU: validate_url_for_ssrf resolves and approves the attacker-supplied X-Atlassian-Jira-Url / X-Atlassian-Confluence-Url host once at middleware time, but the actual HTTP client re-resolves the raw hostname at connect time with no IP pinning, so a DNS-rebinding name can pass validation with a public IP and then resolve to a link-local or RFC1918 address. Exploitation is a documented, publicly described proof-of-concept rather than confirmed in-the-wild activity (no CISA KEV listing), and the vendor has released version 0.22.0 as the fix. | MEDIUM | 6.5 | 0.2% | 32 |
|