MCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in
Affects mcp-atlassianSource GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.17.0 as a priority.
Data as of 17 Nov 2026, 17:34 UTC
- Patch
- Available – fixed in 0.17.0
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Mar 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.17.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 version 0.17.0, the `confluence_download_attachment` MCP tool accepts a `download_path` parameter that is written to without any directory boundary enforcement. An attacker who can call this tool and supply or access a Confluence attachment with malicious content can write arbitrary content to any path the server process has write access to. Because the attacker controls both the write destination and the written content (via an uploaded Confluence attachment), this constitutes for arbitrary code execution (for example, writing a valid cron entry to `/etc/cron.d/` achieves code execution within one scheduler cycle with no server restart required). Version 0.17.0 fixes the issue.
References
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27825.json (opens in a new tab)
- github.com/sooperset/mcp-atlassian/security/advisories/GHSA-xjgw-4wvw-rgm4 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-27825 (opens in a new tab)
- github.com/sooperset/mcp-atlassian/commit/52b9b0997681e87244b20d58034deae89c91631e (opens in a new tab)