The sooperset mcp-atlassian server is vulnerable to unauthenticated file system access and data exfiltration, posing a high risk of sensitive information disclosure.

This vulnerability involves a combination of missing authentication (CWE-306) and path traversal (CWE-22). The streamable HTTP transport fails to validate user identity, allowing unauthenticated network callers to leverage the application's operator credentials and an unrestricted file_path parameter in upload_attachment to access local files.

The ability for an unauthenticated remote attacker to read arbitrary files accessible to the MCP process can lead to the compromise of sensitive credentials, configuration files, or proprietary business data. By exfiltrating this data through Jira or Confluence, the attacker may gain further unauthorized access to internal Atlassian workflows. With a CVSS score of 8.6, this high-severity vulnerability represents a significant risk to organizational data confidentiality.

Immediate Action: Update the mcp-atlassian package to version 0.22.0 or later to implement necessary authentication checks and restrict file path inputs.

Proactive Monitoring: Review application logs for unauthorized access patterns or unexpected file read requests, particularly those originating from the streamable HTTP transport endpoint.

Compensating Controls: Deploy a Web Application Firewall (WAF) or network access control list to restrict access to the MCP server endpoint to authorized internal IP addresses only.

Public Exploit Available: Unknown

This vulnerability presents a severe risk due to the lack of authentication required for an attacker to interact with the underlying file system. Organizations utilizing mcp-atlassian must prioritize the update to version 0.22.0 immediately to remediate the exposure. Failure to patch allows for potential information theft and unauthorized data movement within integrated Atlassian environments.