Sooperset mcp-atlassian
MCP Atlassian: Incomplete fix for CVE-2026-27826: DNS rebinding bypasses SSRF validation (validated IP not pinned)
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, validate_url_for_ssrf checks a hostname's resolved addresses, but Requests and urllib3 resolve the hostname again when connecting. A caller can use a short-lived DNS answer that is public during validation and private during connection, preserving unauthenticated access to internal or metadata endpoints despite the earlier CVE-2026-27826 remediation. The advisory traces the vulnerable input and processing flow through validate_url_for_ssrf, _check_dns_resolution, socket.getaddrinfo, and _make_ssrf_safe_hook, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.22.0
Fixed in 0.22.0
Mitigation
Upgrade mcp-atlassian to 0.22.0 or later.
References
- Vendor advisory github.com/sooperset/mcp-atlassian/security/ad…
- Patch github.com/sooperset/mcp-atlassian/pull/1448
- Patch github.com/sooperset/mcp-atlassian/commit/b041…
1 more
- Release notes github.com/sooperset/mcp-atlassian/releases/ta…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.