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

Description mcp-atlassian deploys in two common patterns: Pattern A single-user, server-side credentials: operator sets JIRAUSERNAME + JIRAAPITOKEN or CONFLUENCEUSERNAME + CONFLUENCEAPITOKEN in environment variables. Server uses these to call Jira/Confluence. This is the documented quickstart...

CVE-2026-77261

MCP Atlassian is a Model Context Protocol MCP server for Atlassian products Confluence and Jira. Prior to 0.22.0, makessrfsafehook is omitted from JiraFetcher and ConfluenceFetcher sessions created through the basic-auth and oauthpat branches. If an attacker-controlled or compromised configured...

EUVD-2026-84631

MCP Atlassian is a Model Context Protocol MCP server for Atlassian products Confluence and Jira. Prior to 0.22.0, makessrfsafehook is omitted from JiraFetcher and ConfluenceFetcher sessions created through the basic-auth and oauthpat branches. If an attacker-controlled or compromised configured...

CVE-2026-77261

The MCP Atlassian Model Context Protocol server (versions prior to 0.22.0 ) is vulnerable to Server-Side Request Forgery (SSRF) due to a missing _make_ssrf_safe_hook in the JiraFetcher and ConfluenceFetcher sessions. Specifically, sessions created via the basic-auth and oauth_pat branches can be ...