CVE-2026-77265
MEDIUMMCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, header-supplied Jira or Confluence URLs are resolved and validated before the HTTP client resolves the hostname again for the connection. An unauthenticated caller can use a...
Full CISO analysis pending enrichment.
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| MCP Atlassian | pip | — | No patch |
Do you use MCP Atlassian? You're affected.
How severe is it?
What is the attack surface?
What should I do?
No patch available
Monitor for updates. Consider compensating controls or temporary mitigations.
Which compliance frameworks are affected?
Compliance analysis pending. Sign in for full compliance mapping when available.
Frequently Asked Questions
What is CVE-2026-77265?
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, header-supplied Jira or Confluence URLs are resolved and validated before the HTTP client resolves the hostname again for the connection. An unauthenticated caller can use a DNS-rebinding hostname that returns a public address during validation and an internal address during connection, causing requests to internal or metadata services. The advisory traces the vulnerable input and processing flow through X-Atlassian-Jira-Url, X-Atlassian-Confluence-Url, validate_url_for_ssrf, and DNS rebinding, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
Is CVE-2026-77265 actively exploited?
No confirmed active exploitation of CVE-2026-77265 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-77265?
No patch is currently available. Monitor vendor advisories for updates.
What is the CVSS score for CVE-2026-77265?
CVE-2026-77265 has a CVSS v3.1 base score of 5.9 (MEDIUM).
What are the technical details?
Original Advisory
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, header-supplied Jira or Confluence URLs are resolved and validated before the HTTP client resolves the hostname again for the connection. An unauthenticated caller can use a DNS-rebinding hostname that returns a public address during validation and an internal address during connection, causing requests to internal or metadata services. The advisory traces the vulnerable input and processing flow through X-Atlassian-Jira-Url, X-Atlassian-Confluence-Url, validate_url_for_ssrf, and DNS rebinding, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
Weaknesses (CWE)
CWE-918 — Server-Side Request Forgery (SSRF): 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.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N References
- github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460 x_refsource_MISC
- github.com/sooperset/mcp-atlassian/pull/1448 x_refsource_MISC
- github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0 x_refsource_MISC
- github.com/sooperset/mcp-atlassian/security/advisories/GHSA-49xv-9743-pw8w x_refsource_CONFIRM
Timeline
Related Vulnerabilities
CVE-2026-77244 10.0 Analysis pending
Same package: mcp-atlassian CVE-2026-27825 9.1 mcp-atlassian: Path Traversal enables file access
Same package: mcp-atlassian CVE-2026-77243 8.8 Analysis pending
Same package: mcp-atlassian CVE-2026-27826 8.2 mcp-atlassian: SSRF allows internal network access
Same package: mcp-atlassian GHSA-wm45-qh3g-v83f 7.7 mcp-atlassian: path traversal leaks server files+creds
Same package: mcp-atlassian