MCP Atlassian: Path traversal in upload_attachment allows arbitrary file read and exfiltration via MCP tool call
CVE-2026-77266 · GHSA-mfv2-4wvm-9pgp · 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
Any authenticated MCP client — including a compromised AI agent, a prompt-injected session, or a malicious plugin — can read and exfiltrate arbitrary files readable by the server process: /etc/shadow — system password hashes /proc/self/environ — process environment variables (API keys, secrets) ~/.mcp-atlassian/oauth-.json — stored OAuth refresh tokens SSH private keys, TLS certificates, application configuration files No special privileges beyond standard MCP tool access are required. The vulnerability affects both HTTP-mode (multi-user) and stdio-mode (local) deployments. Both the jirauploadattachment and confluenceuploadattachment MCP tools are affected.
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.
| 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.