CVE-2026-77255 json
MCP Atlassian: Arbitrary File Read & Exfiltration (Confused Deputy) in JIRA update_issue
published last mo. modified last mo. also EUVD-2026-84746 , GHSA-2xj6-xx86-cwwc , PYSEC-2026-4080
- cvss
- 8.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- 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 Jira update_issue attachments argument is converted into local paths and routed to the attachment upload implementation without workspace validation. A caller can make the MCP server read arbitrary local files and attach them to a Jira issue, using the server as a confused deputy to exfiltrate the contents. The advisory traces the vulnerable input and processing flow through jira update_issue, attachments, upload_attachment, and file_path, 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-77255 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
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-2xj6-xx86-cwwc referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N |
| GitHub | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N |
| OSV | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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, issue-tracking, patch
-
github.com
/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460
web, patch
-
github.com
/sooperset/mcp-atlassian/security/advisories/GHSA-2xj6-xx86-cwwc
exploit, web, vendor-advisory
-
github.com
/sooperset/mcp-atlassian/releases/tag/v0.22.0
web, release-notes
-
github.com
/sooperset/mcp-atlassian
package
-
pypi.org
/project/mcp-atlassian
package
-
github.com
/advisories/GHSA-2xj6-xx86-cwwc
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-77255
advisory
Sources
- CVE List CVE-2026-77255
- GitHub Advisory GHSA-2xj6-xx86-cwwc
- NVD CVE-2026-77255
- OSV PYSEC-2026-4080
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.