UTC
Critical

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

CVE-2026-77244 · GHSA-wrhw-j3f9-8vc6 · published 2026-09-22

Severity
Critical
CVSS score
10.0
Chance of exploitation (EPSS)
0.35%
Fixed in
0.22.0
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Total
  • CISA SSVC
What it is

Attacker profile: any party with network reach to the HTTP transport. No credentials, no prior account, no privileged position required. Typical deployment patterns at risk: Docker compose with port exposed (very common in mcp-atlassian's Cloud-deployed MCP server behind a load balancer where the LB Internal corporate network where any employee can reach the server Misconfigured Kubernetes ingress Tunneled MCP server via ngrok / Cloudflare Tunnel for development Security impact after exploitation: 1. Full Jira read access. Every project, every issue, every comment, every attachment, every user — using the operator's API token. 2. Full Jira write access. Create, edit, delete issues. …

What to do

Upgrade mcp-atlassian to 0.22.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

The most direct fix is the standard MCP-server-with-env-creds pattern: 1. When OAUTH_PROXY_ENABLE_ENV is not set, REFUSE to start the HTTP 2. Even with SINGLE_USER_MODE, bind the HTTP transport to 127.0.0.1 3. Document the multi-tenant pattern as requiring OAuth proxy or 4. Replace AtlassianOpaqueTokenVerifier with a verifier that performs Defense in depth: the README quickstart should not encourage exposing the HTTP transport without auth. The docker-compose.yml in the repo should bind to 127.0.0.1 only by default.

Affected
PackageRegistryAffectedFixed in
mcp-atlassianPyPI< 0.22.00.22.0

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].