MCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in confluence_download_attachm
CVE-2026-27825 · GHSA-xjgw-4wvw-rgm4 · published 2026-03-10
- Severity
- Critical
- CVSS score
- 9.0
- Chance of exploitation (EPSS)
- 12.3%
- Fixed in
- 0.17.0
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
An attacker who can invoke MCP tools and upload (or access) a Confluence attachment with controlled content can achieve arbitrary code execution on the server host. The MCP HTTP transport endpoints carry no authentication by default, meaning any host that can reach the server's HTTP port can call tools using the server's own embedded Confluence credentials (global fallback). The default HOST=0.0.0.0 binding makes this reachable from the local network without any configuration change. In enterprise deployments where Confluence write access is broadly granted, the effective attacker prerequisite reduces to network access to the MCP HTTP port.
Upgrade mcp-atlassian to 0.17.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mcp-atlassian | PyPI | < 0.17.0 | 0.17.0 |
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
- Critical[mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty tokenmcp-atlassian
- HighMCP Atlassian: Arbitrary File Read & Exfiltration (Confused Deputy) in JIRA update_issuemcp-atlassian
- HighMCP Atlassian: ENABLED_TOOLS / Toolset authorization bypassmcp-atlassian
- Highmcp-atlassian has an incomplete SSRF remediationmcp-atlassian
- HighMCP Atlassian: SSRF redirect protection missing for basic-auth and OAuth authentication branchesmcp-atlassian
- HighMCP Atlassian: Arbitrary file read via confluence_upload_attachment allows exfiltration of server credentialsmcp-atlassian
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.