CVE-2026-77260 json
MCP Atlassian: Arbitrary local file READ via unconstrained file_path in upload_attachment (Confluence + Jira)
published last mo. modified last mo. also EUVD-2026-84630 , GHSA-f4p7-qx46-wc5j , PYSEC-2026-4091
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- 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 Confluence and Jira upload_attachment implementations accept an unconstrained file_path and open the referenced server-local file. A permitted MCP caller can upload sensitive host files to an Atlassian destination and then retrieve their contents. The advisory traces the vulnerable input and processing flow through upload_attachment, file_path, and CVE-2026-27825, 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-77260 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
- total
- Assessed
- last mo.
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-f4p7-qx46-wc5j referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N |
| CNA | 4.0 | 8.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
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-f4p7-qx46-wc5j
exploit, web, mitigation, vendor-advisory
-
github.com
/sooperset/mcp-atlassian/releases/tag/v0.22.0
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-77260
advisory
-
github.com
/sooperset/mcp-atlassian
package
-
pypi.org
/project/mcp-atlassian
package
-
github.com
/advisories/GHSA-f4p7-qx46-wc5j
advisory
Sources
- CVE List CVE-2026-77260
- GitHub Advisory GHSA-f4p7-qx46-wc5j
- NVD CVE-2026-77260
- OSV PYSEC-2026-4091
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.