MCP Atlassian: Arbitrary File Read via Upload Attachment Tools
CVE-2026-77270 · GHSA-f26r-j276-ggg4 · published 2026-09-22
- Severity
- Medium
- CVSS score
- 6.5
- Chance of exploitation (EPSS)
- 0.50%
- Fixed in
- 0.22.0
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
Arbitrary file read: Any file readable by the server process can be exfiltrated via both Confluence and Jira upload paths Credential theft: Environment files (.env), SSH keys (~/.ssh/), OAuth tokens (~/.mcp-atlassian/), and application configs can be stolen Prompt injection amplification: Malicious content in Jira/Confluence can trigger file exfiltration via the AI assistant Write tools require authentication: The @checkwriteaccess decorator enforces READONLYMODE, but when write access is allowed, any authenticated user can upload any file Both services affected: The vulnerability exists independently in both the Confluence and Jira attachment upload code paths
Upgrade mcp-atlassian to 0.22.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.
Call validatesafepath before reading the file in both upload methods: Confluence fix (src/mcpatlassian/confluence/attachments.py): Jira fix (src/mcpatlassian/jira/attachments.py):
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mcp-atlassian | PyPI | < 0.22.0 | 0.22.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
- CriticalMCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in confluence_download_attachmmcp-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
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.