CVE-2026-77244 json
[mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty token
published last mo. modified last mo. also EUVD-2026-84607 , GHSA-wrhw-j3f9-8vc6 , PYSEC-2026-4103
- cvss
- 10.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi mcp-atlassian 0.22.0
- sooperset mcp_atlassian 0.22.0
- mcp-atlassian mcp_atlassian 0.22.0
Is CVE-2026-77244 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last mo.
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-wrhw-j3f9-8vc6 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N |
| GitHub | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N |
| OSV | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | mcp-atlassian | <0.22.0 |
0.22.0 |
Affected products
- sooperset mcp-atlassian
Classification
References
-
github.com
/sooperset/mcp-atlassian/pull/1448
web, patch
-
github.com
/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460
web, patch
-
github.com
/sooperset/mcp-atlassian/security/advisories/GHSA-wrhw-j3f9-8vc6
web, exploit, vendor-advisory
-
github.com
/sooperset/mcp-atlassian/releases/tag/v0.22.0
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-77244
advisory
-
github.com
/sooperset/mcp-atlassian
package
-
pypi.org
/project/mcp-atlassian
package
-
github.com
/advisories/GHSA-wrhw-j3f9-8vc6
advisory
Sources
- CVE List CVE-2026-77244
- GitHub Advisory GHSA-wrhw-j3f9-8vc6
- NVD CVE-2026-77244
- OSV PYSEC-2026-4103
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.