What’s Vulnerable › Vulnerabilities

CVE-2026-77244: [mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty token

• Severity: critical (CVSS 10.0 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.3% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2026-09-22 · updated 2026-09-29
• Weakness: CWE-287

Description

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.

Affected products

• sooperset mcp-atlassian: before 0.22.0 — fixed in 0.22.0

How to fix

Upgrade to a fixed version: sooperset mcp-atlassian 0.22.0. Check the vendor advisory for mitigations.

References

• https://github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460
• https://github.com/sooperset/mcp-atlassian/pull/1448
• https://github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0
• https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-wrhw-j3f9-8vc6

Get alerted when CVE-2026-77244 or the next vulnerability affects your stack