CVE-2026-77259 json
MCP Atlassian: Arbitrary file read via confluence_upload_attachment allows exfiltration of server credentials
published last mo. modified last mo. also EUVD-2026-84758 , GHSA-6cr4-ccf3-x7h4 , PYSEC-2026-4086
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- 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, confluence_upload_attachment opens a caller-selected server-local file without checking that the resolved path remains in the workspace. A caller can upload environment files, credentials, or other readable host data to a Confluence page and retrieve it through Atlassian. The advisory traces the vulnerable input and processing flow through confluence_upload_attachment, file_path, and open(file_path, "rb"), 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-77259 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.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-6cr4-ccf3-x7h4 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| GitHub | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| OSV | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/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-6cr4-ccf3-x7h4
exploit, web, mitigation, 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-6cr4-ccf3-x7h4
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-77259
advisory
Sources
- CVE List CVE-2026-77259
- GitHub Advisory GHSA-6cr4-ccf3-x7h4
- NVD CVE-2026-77259
- OSV PYSEC-2026-4086
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.