CVE-2026-77253 json
MCP Atlassian: Jira and Confluence attachment upload tools can read arbitrary server-local files
published last mo. modified last mo. also EUVD-2026-84742 , GHSA-vc25-24vv-fxxm , PYSEC-2026-4101
- cvss
- 7.1
- 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 39%
- 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, Jira and Confluence attachment upload tools accept arbitrary local filesystem paths and send the selected bytes to Atlassian. In HTTP or multi-user deployments, a caller can cross the client-to-server filesystem boundary and disclose configuration, credentials, mounted secrets, or other files readable by the MCP process. The advisory traces the vulnerable input and processing flow through jira_upload_attachment, confluence_upload_attachment, file_path, and server-local filesystem, 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-77253 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 39% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-vc25-24vv-fxxm referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N |
| GitHub | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N |
| OSV | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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-vc25-24vv-fxxm
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-vc25-24vv-fxxm
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-77253
advisory
Sources
- CVE List CVE-2026-77253
- GitHub Advisory GHSA-vc25-24vv-fxxm
- NVD CVE-2026-77253
- OSV PYSEC-2026-4101
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.