The MCP Atlassian server interprets user‑controlled file_path arguments without validating them. A malicious client can supply a path that points to any file on the host and cause the server to read that file, then package it as an attachment to be served back to the client in Confluence or Jira. The flaw permits remote read of server files, exposing confidential data and potentially giving an attacker insight into the underlying infrastructure. This vulnerability is classified under CWE‑73, indicating a path traversal or unrestricted file read flaw.

Affected systems include any deployment of the MCP Atlassian server (Confluence and Jira integration) running a version prior to 0.22.0. The short‑description indicates that the vulnerability exists in the upload tools of Confluence and Jira via the MCP server. All clients that have permission to upload attachments on the MCP server are susceptible. The specific product is sooperset:MCP Atlassian, with the version range of anything less than 0.22.0.

The CVSS score of 8.3 places this issue in the high severity range. EPSS is not available, so the exact exploitation probability is unknown, but the lack of known public exploits and absence from the CISA KEV list suggest the risk is lower than similar high‑severity flaws that are actively exploited. However, because the flaw allows the reading of arbitrary files, any user who can reach the MCP server can potentially gain access to sensitive data. The attack vector appears to be from an authenticated or otherwise authorized user within the network or the same client that can issue upload requests, rather than a publicly exposed HTTP endpoint. Administrators should treat this as a high‑risk door that could enable attackers to exfiltrate host information.