Quick answers
- Is CVE-2026-77266 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77266 being exploited in the wild.
- How severe is CVE-2026-77266?
- Medium severity, with a CVSS score of 6.5, published 22 September 2026.
- Which products and versions are affected?
- mcp-atlassian (PyPI) < 0.22.0, ECOSYSTEM:introduced=0,fixed=0.22.0.
- Is there a fix for CVE-2026-77266?
- Yes. mcp-atlassian (PyPI): upgrade to 0.22.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77266 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-77266?
- Check whether you run mcp-atlassian (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- mcp-atlassian (PyPI): upgrade to 0.22.0 or later
pip install "mcp-atlassian>=0.22.0"
Technical details
This is a path traversal vulnerability in the upload_attachment() functions of both the Jira and Confluence modules (mcp_atlassian/jira/attachments.py and mcp_atlassian/confluence/attachments.py). The functions accept a user-controlled file_path parameter and open the file for reading without calling validate_safe_path(), unlike the corresponding download functions which were protected in a prior fix (GHSA-xjgw-4wvw-rgm4). An authenticated MCP client can supply arbitrary paths (e.g., /etc/passwd, /proc/self/environ, ~/.mcp-atlassian/oauth-*.json) causing the server process to read and transmit the file's contents to the remote Atlassian instance as an attachment. No special privileges beyond standard MCP tool access are required. The vulnerability is reachable over the network in HTTP-mode deployments and locally in stdio-mode, affecting both jira_upload_attachment and confluence_upload_attachment MCP tools.
Affected products
- Atlassian MCP Atlassian up to v0.21.1
Identifiers
- CVE-2026-77266
- GHSA-mfv2-4wvm-9pgp
- PYSEC-2026-4097
Timeline
- 2026-09-22: disclosed: GHSA-mfv2-4wvm-9pgp published
- 2026: other: CVE-2026-77266 assigned