MCP Atlassian: HTTP upload tools accept arbitrary server-local file paths
CVE-2026-77257 · GHSA-mrq8-fv7v-hhjg · published 2026-09-22
- Severity
- High
- CVSS score
- 8.3
- Chance of exploitation (EPSS)
- 0.39%
- Fixed in
- 0.22.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
Impact is local file disclosure through an authenticated Atlassian attachment write. In Docker/Kubernetes deployments that mount .env or token material into the service, exposed files may include API tokens, OAuth credentials, service configuration, or other local secrets readable by the MCP process. The issue is bounded by tool access and Atlassian permissions: the attacker needs an MCP call path to a write tool and an issue/page where the attachment can be written. It is not direct RCE. Severity is Medium-to-High depending on deployment: Medium for single-user/local stdio usage or tightly scoped tokens.
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.