Am I affected by Authentication bypass in mcp-atlassian HTTP transport? What should I do?
The token checker AtlassianOpaqueTokenVerifier accepts any non-empty text as a valid token.
Affected: mcp-atlassian < 0.22.0. Fixed in: 0.22.0. What should you check, and what should you do about it?
Full incident page with sources: https://agentarmorhq.com/incidents/2026/09/cve-2026-77244-mcp-atlassian (opens external site)
1 answer
Am I affected? Affected: mcp-atlassian < 0.22.0. Fixed in: 0.22.0.
- Check your version: run
pip show mcp-atlassian. Versions < 0.22.0 of mcp-atlassian are affected.
What to do now
- Upgrade to the fixed version: run
pip install --upgrade "mcp-atlassian>=0.22.0"(first patched version 0.22.0). - Do not expose the HTTP transport without authentication.
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
Sources
- GitHub Advisory Database: https://github.com/advisories/GHSA-wrhw-j3f9-8vc6 (opens external site)
Full incident page: https://agentarmorhq.com/incidents/2026/09/cve-2026-77244-mcp-atlassian (opens external site)
Did this work for you?- Check your version: run