CVE-2026-77254: sooperset mcp-atlassian · Missing Authentication
Affects sooperset mcp-atlassianSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.22.0 as a priority.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.22.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 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 6 Nov 2026.
What to do
Upgrade mcp-atlassian and sooperset/mcp-atlassian to 0.22.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| soopersetmcp-atlassian | Affected
| Fixed in
|
GitHubsooperset/mcp-atlassianpkg:github/sooperset/mcp-atlassianOther 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
Upgrade MCP Atlassian to version 0.22.0 or later, where the vulnerability is fixed. Deployments should ensure that an independent authentication boundary is in place to prevent unauthenticated access to critical functions. Since this is a self-hosted product, remediation requires applying the official fix by upgrading. No vendor advisory link is provided, so check the official sooperset project resources for the patch and further guidance.
Description
CVE-2026-77254 is a critical vulnerability in sooperset's MCP Atlassian server prior to version 0.22.0. It allows unauthenticated network callers to perform operations with operator-level permissions by exploiting missing authentication on the HTTP MCP endpoint. The flaw permits requests without per-user identity to reach tool handlers that use globally configured Jira or Confluence credentials. This issue is resolved in version 0.22.0.
References
- github.com/sooperset/mcp-atlassian/security/advisories/GHSA-vc8m-84rp-53hx (opens in a new tab)
- github.com/sooperset/mcp-atlassian/pull/1448 (opens in a new tab)
- github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460 (opens in a new tab)
- github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0 (opens in a new tab)