CVE-2026-77258
highpriority · track · 0EPSS 0.004 · 31 %ileUSEPSS · scored 2026-10-27
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, upload_attachment in src/mcp_atlassian/confluence/attachments.py accepts a caller-controlled file_path and opens the selected server-local file without restricting it to the workspace. A permitted Confluence MCP caller can upload the file as an attachment and disclose data readable by the server process. This issue is fixed in version 0.22.0.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (2)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- GHSA-93xw-j965-9mx3MCP Atlassian: Arbitrary file read/exfiltration via upload_attachment missing validate_safe_path()2026-09-22ghsa · osvUS
## Summary The `upload_attachment` method in `confluence/attachments.py` reads and uploads arbitrary local files to Confluence without calling `validate_safe_path()`. Both download methods (`download_attachment` at line 223, `download_content_attachments` at line 272) correctly call `validate_safe_path()` before writing files, but the upload path at lines 35-79 skips this check entirely. An AI agent connected via MCP (or an attacker influencing that agent through prompt injection) can read any file on the host and exfiltrate it by uploading it as a Confluence page attachment. ## Vulnerable Code File: `src/mcp_atlassian/confluence/attachments.py`, lines 62-79 ```python # No validate_safe_path() call anywhere in this method if not os.path.isabs(file_path): file_path = os.path.abspath(file_path) if not os.path.exists(file_path): return {"success": False, "error": f"File not found: {file_path}"} filename = os.path.basename(file_path) attachment = self._upload_attachment_direct( content_id, file_path, filename, comment, minor_edit ) ``` The `validate_safe_path` function is already imported at line 9 of the same file, and used in the download methods. It was just not added to the upload path. ## Proof of Concept Tested with mcp-atlassian 0.21.1 on Python 3.11 (EC2, Amazon Linux 2023). ```python import inspect from mcp_atlassian.confluence.attachments import AttachmentsMixin # Confirm: no validate_safe_path in upload source = inspect.getsource(AttachmentsMixin.upload_attachment) assert "validate_safe_path" not in source # passes # Confirm: validate_safe_path IS in downloads assert "validate_safe_path" in inspect.getsource(AttachmentsMixin.download_attachment) # passes assert "validate_safe_path" in inspect.getsource(AttachmentsMixin.download_content_attachments) # passes ``` An MCP tool call like this reads /etc/passwd and uploads it to Confluence: ```json {"tool": "confluence_upload_attachment", "arguments": {"content_id": "123456", "file_path": "/etc/passwd"}} ``` ## Impact Exfiltration of any file readable by the MCP server process: SSH keys, AWS credentials, .env files, /etc/passwd, application secrets. Data leaves the local machine and lands on a remote Confluence instance accessible to other users. ## Suggested Fix Add `validate_safe_path(file_path)` before the `os.path.exists()` check in `upload_attachment`, matching the existing pattern in the download methods. The function is already imported.
- PYSEC-2026-4088MCP Atlassian: Arbitrary file read/exfiltration via upload_attachment missing validate_safe_path()2026-10-01vendor · osvUS
## Summary The `upload_attachment` method in `confluence/attachments.py` reads and uploads arbitrary local files to Confluence without calling `validate_safe_path()`. Both download methods (`download_attachment` at line 223, `download_content_attachments` at line 272) correctly call `validate_safe_path()` before writing files, but the upload path at lines 35-79 skips this check entirely. An AI agent connected via MCP (or an attacker influencing that agent through prompt injection) can read any file on the host and exfiltrate it by uploading it as a Confluence page attachment. ## Vulnerable Code File: `src/mcp_atlassian/confluence/attachments.py`, lines 62-79 ```python # No validate_safe_path() call anywhere in this method if not os.path.isabs(file_path): file_path = os.path.abspath(file_path) if not os.path.exists(file_path): return {"success": False, "error": f"File not found: {file_path}"} filename = os.path.basename(file_path) attachment = self._upload_attachment_direct( content_id, file_path, filename, comment, minor_edit ) ``` The `validate_safe_path` function is already imported at line 9 of the same file, and used in the download methods. It was just not added to the upload path. ## Proof of Concept Tested with mcp-atlassian 0.21.1 on Python 3.11 (EC2, Amazon Linux 2023). ```python import inspect from mcp_atlassian.confluence.attachments import AttachmentsMixin # Confirm: no validate_safe_path in upload source = inspect.getsource(AttachmentsMixin.upload_attachment) assert "validate_safe_path" not in source # passes # Confirm: validate_safe_path IS in downloads assert "validate_safe_path" in inspect.getsource(AttachmentsMixin.download_attachment) # passes assert "validate_safe_path" in inspect.getsource(AttachmentsMixin.download_content_attachments) # passes ``` An MCP tool call like this reads /etc/passwd and uploads it to Confluence: ```json {"tool": "confluence_upload_attachment", "arguments": {"content_id": "123456", "file_path": "/etc/passwd"}} ``` ## Impact Exfiltration of any file readable by the MCP server process: SSH keys, AWS credentials, .env files, /etc/passwd, application secrets. Data leaves the local machine and lands on a remote Confluence instance accessible to other users. ## Suggested Fix Add `validate_safe_path(file_path)` before the `os.path.exists()` check in `upload_attachment`, matching the existing pattern in the download methods. The function is already imported.
also known as (2)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (4) nvd
External citations — patches, advisories, analysis.
- https://github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460Patch
- https://github.com/sooperset/mcp-atlassian/pull/1448Issue TrackingPatch
- https://github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0Release Notes
- https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-93xw-j965-9mx3ExploitVendor Advisory
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan