The sooperset mcp-atlassian server is vulnerable to unauthenticated Server-Side Request Forgery due to authority confusion, potentially exposing internal network resources.

This is a Server-Side Request Forgery (SSRF) vulnerability (CWE-918) caused by inconsistent parsing of backslash-delimited authorities between the validation logic and the underlying HTTP connection layer. An unauthenticated attacker can craft a malicious URL that passes security checks while directing the server to interact with sensitive internal network endpoints.

Successful exploitation permits unauthorized access to internal services that are otherwise shielded from the public internet. Given the CVSS score of 8.8, this high-severity flaw could lead to the exposure of confidential Atlassian configuration data, internal API access, or sensitive metadata, significantly increasing the risk of lateral movement within the corporate network.

Immediate Action: Upgrade the mcp-atlassian package to version 0.22.0 or later immediately to resolve the URL validation logic error.

Proactive Monitoring: Review web server and application logs for suspicious outbound requests originating from the mcp-atlassian service, specifically monitoring for unusual internal IP addresses or non-standard port connections.

Compensating Controls: Implement strict egress filtering on the host running the MCP server to prevent it from initiating connections to sensitive internal subnets or unauthorized external domains.

Public Exploit Available: Unknown

Organizations utilizing mcp-atlassian must prioritize updating to version 0.22.0 to eliminate this SSRF vulnerability. Given the ease of exploitation and the potential for internal network reconnaissance, failure to patch leaves internal Jira and Confluence infrastructure exposed to unauthorized access. Apply the update as part of the next immediate maintenance cycle.