CVE-2026-77251: sooperset mcp-atlassian · Hardware Child Block Incorrectly Connected to Parent System
Affects sooperset mcp-atlassianSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 0.22.0 soon.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.22.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA: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 5 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 this vulnerability is fixed. No other mitigation is specified or required according to the advisory. Patch status is confirmed fixed in 0.22.0.
Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, Jira search accepts a forbidden project clause because it checks only for the presence of project syntax, Confluence search uses an incomplete case-sensitive space check, and Jira board APIs omit project-filter enforcement. These paths expose issues, boards, or pages outside JIRA_PROJECTS_FILTER or CONFLUENCE_SPACES_FILTER when the operator credentials have broader access. The advisory traces the vulnerable input and processing flow through jira_search, confluence_search, get_board_issues, get_agile_boards, JIRA_PROJECTS_FILTER, and CONFLUENCE_SPACES_FILTER, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
References
- github.com/sooperset/mcp-atlassian/security/advisories/GHSA-w66g-j6c4-hcfc (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)