AAK-MCP-ATLASSIAN-CVE-2026-124503-001: mcp-atlassian 0.22.0 to 0.24.0: the attachment upload guard is the working directory, so a wide one passes any file
- Severity
- HIGH
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
McpAtlassianUploadGuardWorkingDirectory
What it detects
MCP Atlassian (mcp-atlassian, sooperset/mcp-atlassian) 0.22.0 confined the source path of the Confluence and Jira attachment uploads with validate_safe_path, but the guard's boundary is the process's working directory. A server on the SSE or streamable-HTTP transport started from / (a systemd system unit with no WorkingDirectory=) or from a home directory (a systemd user unit, or the documented uvx launch from a shell) therefore accepts any file below it, so an authenticated remote caller of confluence_upload_attachment reads files such as /proc/self/environ, which holds the server's Atlassian tokens, and receives them as an attachment in their own Confluence (CVE-2026-124503, GHSA-qh7q-jmc7-rc7j; CVSS 3.1 4.3 in the CVE record, 7.7 in the project's advisory, CWE-22). Checked in the source at the release tags: the upload call sites pass no base directory from 0.22.0 to 0.24.0, and 0.24.1 confines file paths to MCP_ATLASSIAN_FILES_DIR, or on a remote transport to ~/.mcp-atlassian/files, and refuses a filesystem root or home directory. The project's image sets WORKDIR /app, which holds, and it treats stdio reads of local files as intended.
How to fix
Upgrade mcp-atlassian to 0.24.1 or later and pin it, and on an SSE or streamable-HTTP deployment set MCP_ATLASSIAN_FILES_DIR to a dedicated directory. Until you upgrade, start a remote server from a dedicated, empty working directory (WorkingDirectory= in a systemd unit), never / or a home directory.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-ATLASSIAN-CVE-2026-124503-001
Limitations
Reads mcp-atlassian from 0.22.0 below 0.24.1 where a requirements*.txt entry at any depth, or at the project root a pyproject.toml, Pipfile, lockfile or uvx launch in an MCP config, states the version, judging a range by the versions it admits. latest is 0.24.1, fixed, so a reference that states no version is not reported. It reads the version, not the transport or the working directory, so a stdio launch, which the project treats as reading local files by design, and a remote server started from a dedicated directory are reported too. The ghcr.io/sooperset/mcp-atlassian image is not read for this rule: it sets WORKDIR /app, so a container started with another working directory (docker run -w /) is not reported. Releases below 0.22.0 had no upload guard at all, which AAK-MCP-ATLASSIAN-CVE-2026-73498-001 reports. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.
References
- CVE: CVE-2026-124503
- OWASP MCP Top 10: MCP05:2025 (Command Injection & Execution), MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
- OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-INJECT-06 (Tool Param Path Traversal)
- CSA AI Controls Matrix (AICM): AIS-07, STA-08
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-ATLASSIAN-CVE-2026-124503-001.md: the page then shows that text, with the registry reference appended under it.