CVE-2026-77246: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in sooperset mcp-atlassian
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, an HTTP transport deployment with READ_ONLY_MODE=false accepts a request without an Authorization identity and permits attacker-controlled Atlassian service headers, including X-Atlassian-Confluence-Url, to select a public attacker hostname or one allowed by MCP_ALLOWED_URL_DOMAINS. A caller can then invoke confluence_upload_attachment or the Jira attachment variant in src/mcp_atlassian/jira/attachments.py with a server-local file_path and cause the MCP process to send the file to the selected attachment endpoint. This issue is fixed in version 0.22.0.
AI Analysis
Technical Summary
The vulnerability exists in MCP Atlassian, a Model Context Protocol server for Atlassian products such as Confluence and Jira. When deployed with READ_ONLY_MODE=false, the server accepts requests without an Authorization identity and permits attacker-controlled Atlassian service headers, including X-Atlassian-Confluence-Url. This allows an attacker to select a public hostname or one allowed by MCP_ALLOWED_URL_DOMAINS. The attacker can invoke confluence_upload_attachment or the Jira attachment variant with a server-local file_path, causing the MCP process to send the file to the selected attachment endpoint. This improper limitation of a pathname to a restricted directory (CWE-22) leads to unauthorized file disclosure. The vulnerability is resolved in version 0.22.0.
Potential Impact
An unauthenticated attacker can cause the MCP process to send arbitrary local files to an attacker-controlled endpoint, resulting in high confidentiality impact. There is no impact on integrity or availability. This could lead to unauthorized disclosure of sensitive files on the server.
Mitigation Recommendations
Upgrade to version 0.22.0 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
CVE-2026-77246: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in sooperset mcp-atlassian
Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, an HTTP transport deployment with READ_ONLY_MODE=false accepts a request without an Authorization identity and permits attacker-controlled Atlassian service headers, including X-Atlassian-Confluence-Url, to select a public attacker hostname or one allowed by MCP_ALLOWED_URL_DOMAINS. A caller can then invoke confluence_upload_attachment or the Jira attachment variant in src/mcp_atlassian/jira/attachments.py with a server-local file_path and cause the MCP process to send the file to the selected attachment endpoint. This issue is fixed in version 0.22.0.
CVSS v3.1
Score 7.4high
Affected software
sooperset
mcp-atlassian
pkg:github/sooperset/mcp-atlassianRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists in MCP Atlassian, a Model Context Protocol server for Atlassian products such as Confluence and Jira. When deployed with READ_ONLY_MODE=false, the server accepts requests without an Authorization identity and permits attacker-controlled Atlassian service headers, including X-Atlassian-Confluence-Url. This allows an attacker to select a public hostname or one allowed by MCP_ALLOWED_URL_DOMAINS. The attacker can invoke confluence_upload_attachment or the Jira attachment variant with a server-local file_path, causing the MCP process to send the file to the selected attachment endpoint. This improper limitation of a pathname to a restricted directory (CWE-22) leads to unauthorized file disclosure. The vulnerability is resolved in version 0.22.0.
Potential Impact
An unauthenticated attacker can cause the MCP process to send arbitrary local files to an attacker-controlled endpoint, resulting in high confidentiality impact. There is no impact on integrity or availability. This could lead to unauthorized disclosure of sensitive files on the server.
Mitigation Recommendations
Upgrade to version 0.22.0 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-20T19:02:23.416Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ab2d105f7a7c541069eacef
Added to database: 09/22/2026, 19:03:33 UTC
Last enriched: 09/22/2026, 19:19:15 UTC
Last updated: 09/23/2026, 01:58:06 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.