CVE-2026-73496: MCP Atlassian · Arbitrary server-side file read via attachment upload
Affects mcp-atlassianSource GCVE Database
Not known to be exploited · CVSS 7.7 High : upgrade to 0.22.0 soon.
Data as of 17 Nov 2026, 17:34 UTC
- Patch
- Available – fixed in 0.22.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 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 16 Nov 2026.
What to do
Upgrade mcp-atlassian to 0.22.0.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewmcp-atlassianpkg:brew/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.
Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, the confluence_upload_attachment and confluence_upload_attachments tools pass a client-controlled file_path through src/mcp_atlassian/confluence/attachments.py upload_attachment, and the jira_update_issue attachments parameter reaches src/mcp_atlassian/jira/attachments.py upload_attachment, without confining either path to an approved server workspace. In a remote HTTP, SSE, or multi-user deployment, absolute or traversing paths are resolved on the MCP server and uploaded to Atlassian, allowing a client with write-tool access to disclose server files, environment-held Atlassian credentials, or another tenant's data. A local single-user stdio deployment does not cross this trust boundary because the server runs in the caller's environment. This issue is fixed in version 0.22.0.
References
- github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0 (opens in a new tab)
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/73xxx/CVE-2026-73496.json (opens in a new tab)
- github.com/sooperset/mcp-atlassian/security/advisories/GHSA-wm45-qh3g-v83f (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-73496 (opens in a new tab)
- github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460 (opens in a new tab)
- github.com/sooperset/mcp-atlassian/pull/1448 (opens in a new tab)