CVE-2026-77244
CRITICALMCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, the HTTP transport accepts requests without a verified user identity and downstream fetcher construction falls back to the operator's globally configured Jira or Confluence...
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-77244?
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, the HTTP transport accepts requests without a verified user identity and downstream fetcher construction falls back to the operator's globally configured Jira or Confluence credentials. A network client that can reach the MCP endpoint can invoke Atlassian tools as the operator, including read and write operations available to that account. The advisory traces the vulnerable input and processing flow through UserTokenMiddleware, AtlassianOpaqueTokenVerifier, _get_fetcher, and streamable-http, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
Is CVE-2026-77244 actively exploited?
No confirmed active exploitation of CVE-2026-77244 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-77244?
No patch is currently available. Monitor vendor advisories for updates.
What is the CVSS score for CVE-2026-77244?
CVE-2026-77244 has a CVSS v3.1 base score of 10.0 (CRITICAL).
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, the HTTP transport accepts requests without a verified user identity and downstream fetcher construction falls back to the operator's globally configured Jira or Confluence credentials. A network client that can reach the MCP endpoint can invoke Atlassian tools as the operator, including read and write operations available to that account. The advisory traces the vulnerable input and processing flow through UserTokenMiddleware, AtlassianOpaqueTokenVerifier, _get_fetcher, and streamable-http, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
Weaknesses (CWE)
CWE-287 Improper Authentication CWE-303 Incorrect Implementation of Authentication Algorithm CWE-862 Missing Authorization CWE-287 — Improper Authentication: When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
- [Architecture and Design] Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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-wrhw-j3f9-8vc6 x_refsource_CONFIRM
Timeline
Related Vulnerabilities
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 GHSA-g5r6-gv6m-f5jv 7.7 mcp-atlassian: path traversal leaks secrets via injection
Same package: mcp-atlassian