CVE-2026-27826

MCP Atlassian has SSRF via unvalidated X-Atlassian-Jira-Url / X-Atlassian-Confluence-Url headers

Published Mar 10, 2026 CVSS 3.1 · 8.2 High EPSS 13.9% KEV · Not listed
Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to version 0.17.0, an unauthenticated attacker who can reach the mcp-atlassian HTTP endpoint can force the server process to make outbound HTTP requests to an arbitrary attacker-controlled URL by supplying two custom HTTP headers without an `Authorization` header. No authentication is required. The vulnerability exists in the HTTP middleware and dependency injection layer — not in any MCP tool handler - making it invisible to tool-level code analysis. In cloud deployments, this could enable theft of IAM role credentials via the instance metadata endpoint (`169[.]254[.]169[.]254`). In any HTTP deployment it enables internal network reconnaissance and injection of attacker-controlled content into LLM tool results. Version 0.17.0 fixes the issue.

Analysis

AI-generated

Technical impact

The MCP Atlassian server, a Model Context Protocol endpoint for Atlassian products, contains a Server Side Request Forgery flaw (CWE‑918). An unauthenticated attacker who can reach the open HTTP endpoint can supply custom X‑Atlassian‑Jira‑Url and X‑Atlassian‑Confluence‑Url headers without any Authorization token; the server blindly follows these headers and initiates outbound HTTP requests to the supplied URLs. This allows arbitrary outbound traffic, enabling internal network discovery, potential theft of IAM role credentials through the instance‑metadata service on cloud hosts, and injection of attacker‑controlled content into LLM tool responses.

Affected Systems

All releases of the MCP Atlassian server distributed by SooperSet before version 0.17.0 are affected.

Risk and Exploitability

Risk and exploitability are high. The CVSS score of 8.2 indicates high severity, and the EPSS score of 14% indicates a higher likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalogue, but because it requires no authentication and accepts arbitrary user input in headers, any host that can reach the exposed HTTP endpoint presents a viable attack vector for internal reconnaissance, credential theft, or manipulation of LLM outputs.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade MCP Atlassian to version 0.17.0 or later to apply the vendor fix.
  • Block or restrict the MCP Atlassian HTTP endpoint to trusted networks or hosts using firewall rules.
  • Deploy a network or proxy filter that inspects and removes or rejects the X‑Atlassian‑Jira‑Url and X‑Atlassian‑Confluence‑Url headers before they reach the server.

Generated by OpenCVE AI on October 25, 2026 at 17:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-7r34-79r5-rcc9 MCP Atlassian has SSRF via unvalidated X-Atlassian-Jira-Url / X-Atlassian-Confluence-Url headers
History
Type Values Removed Values Added
First Time appeared Sooperset mcp Atlassian
CPEs cpe:2.3:a:sooperset:mcp_atlassian:*:*:*:*:*:*:*:*
Vendors & Products Sooperset mcp Atlassian
Type Values Removed Values Added
First Time appeared Sooperset
Sooperset mcp-atlassian
Vendors & Products Sooperset
Sooperset mcp-atlassian
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to version 0.17.0, an unauthenticated attacker who can reach the mcp-atlassian HTTP endpoint can force the server process to make outbound HTTP requests to an arbitrary attacker-controlled URL by supplying two custom HTTP headers without an `Authorization` header. No authentication is required. The vulnerability exists in the HTTP middleware and dependency injection layer — not in any MCP tool handler - making it invisible to tool-level code analysis. In cloud deployments, this could enable theft of IAM role credentials via the instance metadata endpoint (`169[.]254[.]169[.]254`). In any HTTP deployment it enables internal network reconnaissance and injection of attacker-controlled content into LLM tool results. Version 0.17.0 fixes the issue.
Title MCP Atlassian has SSRF via unvalidated X-Atlassian-Jira-Url / X-Atlassian-Confluence-Url headers
Weaknesses CWE-918
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 10, 2026, 7:15 PM
Reserved
Feb 24, 2026, 2:32 AM
Status
Analyzed
Published
Mar 10, 2026, 7:17 PM
Modified
Jun 17, 2026, 10:27 AM