CVE-2026-77267

8.3

Sooperset · mcp-atlassian

A Server-Side Request Forgery (SSRF) vulnerability exists in the mcp-atlassian server, allowing authenticated attackers to access internal or metadata-service URLs via crafted HTTP headers.

Executive summary

An SSRF vulnerability in the Sooperset mcp-atlassian server allows authenticated users to perform unauthorized requests against internal infrastructure, posing a high security risk.

Vulnerability

This is a Server-Side Request Forgery (CWE-918) vulnerability caused by improper validation of the X-Atlassian-Jira-Url and X-Atlassian-Confluence-Url headers. An authenticated attacker can leverage these headers to force the server to interact with sensitive internal resources or cloud metadata services.

Business impact

The exploitation of this vulnerability can lead to significant data compromise or unauthorized access to internal network infrastructure. With a CVSS score of 8.3, this flaw is categorized as high severity because it allows an attacker to bypass perimeter security controls and interact with services that are typically restricted from external access.

Remediation

Immediate Action: Update the mcp-atlassian package to version 0.22.0 or later to ensure the proper implementation of URL validation logic.

Proactive Monitoring: Review application logs for suspicious activity involving the X-Atlassian-Jira-Url or X-Atlassian-Confluence-Url headers, particularly those pointing to internal IP addresses or cloud metadata endpoints.

Compensating Controls: Implement egress filtering on the server hosting the MCP instance to restrict outbound connections to only known, authorized Atlassian API endpoints.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the potential for unauthorized access to internal services, organizations should prioritize the update to version 0.22.0 immediately. Ensuring that this package is patched is critical to maintaining the integrity of the application environment and protecting against internal network reconnaissance.

More Sooperset CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources