MCP Server Security

mcp-atlassian: 25 advisories, one critical, fixed in 0.22.0

GitHub published 25 advisories for the mcp-atlassian server on 22 Sep 2026: one critical (CVE-2026-77244, an HTTP transport authentication bypass), 16 high and 8 medium. Every record lists 0.22.0 as the first patched version. Teams running it over HTTP should check the installed version.

Facts read on .

The critical record, CVE-2026-77244 (GHSA-wrhw-j3f9-8vc6), says the server's HTTP transport token verifier accepted any non-empty token. The advisory describes the exposure for deployments that keep Jira or Confluence credentials in server-side environment variables, the documented quickstart pattern. It gives the vulnerable range as below 0.22.0.

The other 24 records fall into groups the advisories name in their titles: reads of server-local files through attachment upload tools, server-side request forgery and incomplete earlier fixes, a toolset authorization bypass, plaintext OAuth token storage with loose file permissions, and a reflected cross-site scripting issue in the OAuth setup callback.

For an engineer who inventories MCP servers, the practical step is to find every host running the pip package mcp-atlassian, confirm it is at 0.22.0 or later, and check whether the HTTP transport is reachable from anywhere other than the local machine. The count of 25 comes from the GitHub advisory database on 16 Nov 2026.

Sources