MCP Atlassian is a Model Context Protocol (MCP): DNS-rebinding TOCTOU bypass of the SSRF fix (CVE-2026-27826)
Affects mcp-atlassianSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.22.0 when convenient.
Data as of 17 Nov 2026, 17:34 UTC
- Patch
- Available – fixed in 0.22.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade mcp-atlassian to 0.22.0.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewmcp-atlassianpkg:brew/mcp-atlassianOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0 (opens in a new tab)
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/73xxx/CVE-2026-73497.json (opens in a new tab)
- github.com/sooperset/mcp-atlassian/security/advisories/GHSA-489g-7rxv-6c8q (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-73497 (opens in a new tab)
- github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460 (opens in a new tab)
- github.com/sooperset/mcp-atlassian/pull/1448 (opens in a new tab)