Quick answers
- Is CVE-2026-77258 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77258 being exploited in the wild.
- How severe is CVE-2026-77258?
- High severity, with a CVSS score of 7.7, published 22 September 2026.
- Which products and versions are affected?
- mcp-atlassian (PyPI) ECOSYSTEM:introduced=0,fixed=0.22.0; Sooperset Mcp-Atlassian before 0.22.0.
- Is there a fix for CVE-2026-77258?
- 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-77258 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-77258?
- Check whether you run mcp-atlassian (PyPI) or Sooperset Mcp-Atlassian 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
The upload_attachment function in Confluence and Jira modules accepts caller-controlled file paths and opens them without path validation, allowing directory traversal via absolute paths or ../ sequences. An authenticated MCP caller can supply any file path readable by the server process, which is then uploaded and disclosed as an attachment. The fix validates all file paths against the workspace using a validate_safe_path function, confining uploads to the working directory.
Affected products
- sooperset mcp-atlassian before 0.22.0
Identifiers
- CVE-2026-77258
- GHSA-93xw-j965-9mx3
- PYSEC-2026-4088
Timeline
- 2026-09-22: disclosed
- 2026-07-10: patched