sooperset mcp-atlassian up to 0.21.x URL Validation urls.py validate_url_for_ssrf X-Atlassian-Jira-Url/X-Atlassian-Confluence-Url server-side request forgery

Summaryinfo

A vulnerability classified as critical has been found in sooperset mcp-atlassian up to 0.21.x. This vulnerability affects the function validate_url_for_ssrf of the file src/mcp_atlassian/utils/urls.py of the component URL Validation. The manipulation of the argument X-Atlassian-Jira-Url/X-Atlassian-Confluence-Url leads to server-side request forgery. This vulnerability is listed as CVE-2026-73497. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in sooperset mcp-atlassian up to 0.21.x. It has been rated as critical. This issue affects the function validate_url_for_ssrf of the file src/mcp_atlassian/utils/urls.py of the component URL Validation. The manipulation of the argument X-Atlassian-Jira-Url/X-Atlassian-Confluence-Url with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). From 0.17.0 until 0.22.0, validate_url_for_ssrf resolves the attacker-controlled X-Atlassian-Jira-Url and X-Atlassian-Confluence-Url header host once at middleware time, but the outbound request is built with the raw hostname and resolves it again at connection time with no IP pinning. An attacker-controlled DNS-rebinding name can return a public IP during validation and 169.254.169.254 or another internal IP during connection, enabling unauthenticated server-side requests to cloud metadata or internal services. The flaw spans src/mcp_atlassian/utils/urls.py, src/mcp_atlassian/servers/main.py, and src/mcp_atlassian/servers/dependencies.py; validate_url_for_ssrf returns only a verdict rather than a pinned IP, UserTokenMiddleware processes the attacker-controlled headers before fetcher creation, and the Jira and Confluence fetchers use the raw hostname. This issue is fixed in version 0.22.0.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-73497 since 08/12/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 0.22.0 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• sooperset

Name

• mcp-atlassian

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13
• 0.14
• 0.15
• 0.16
• 0.17
• 0.18
• 0.19
• 0.20
• 0.21

Website

• Product: https://github.com/sooperset/mcp-atlassian/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion