Allows unauthenticated network clients to act as the operator for Jira/Confluence, enabling org-wide data modification/exfiltration; affects widely-used Atlassian integrations.
CVE-2026-77244
Unauthenticated MCP server access lets attackers act as operator on Jira/Confluence
Is CVE-2026-77244 being exploited?
Not confirmed. CVE-2026-77244 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-77244?
CVE-2026-77244 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-77244?
Yes. A fix has been recorded for CVE-2026-77244. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-77244 affect?
CVE-2026-77244 affects mcp-atlassian < 0.22.0, Atlassian Jira (via MCP integration), Atlassian Confluence (via MCP integration). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-77244?
Upgrade to mcp-atlassian v0.22.0, restrict MCP network access, rotate operator credentials
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated network requests to MCP can perform read/write actions in Jira/Confluence using operator credentials.
Immediate action required
- affected< 0.22.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.