CVE-2026-77269: Atlassian MCP path traversal in upload_attachment allows arbitrary file read

CVE-2026-77269 · Severity: medium · CVSS 6.5 · Published 2026-09-22

The Atlassian MCP (Model Context Protocol) tool for uploading attachments to Confluence does not properly validate file paths, allowing an attacker to read any file on the server where the MCP process runs. An attacker could access sensitive files like SSH keys, API credentials, environment configuration files, and source code, then exfiltrate them by uploading them to Confluence as attachments. This is a critical data exposure risk for organizations using MCP-enabled Atlassian integrations.

Technologies: mcp-atlassian (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-77269 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-77269 being exploited in the wild.
How severe is CVE-2026-77269?
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-77269?
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-77269 attacked?
It is attacked over the network.
Am I affected by CVE-2026-77269?
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

The vulnerability is a path traversal flaw in the `confluence_upload_attachment` and `confluence_upload_attachments` MCP tools (and the unreachable but similarly flawed Jira `upload_attachment` mixin). The vulnerable code calls `os.path.abspath()` to normalize file paths but fails to invoke the `validate_safe_path()` function that is correctly used in all corresponding download operations. This allows an attacker with access to the MCP tools to specify arbitrary absolute or relative paths (e.g., `/home/user/.ssh/id_rsa`) and read any file accessible to the MCP server process. The fix requires adding a `validate_safe_path()` call to the upload functions, consistent with the incomplete CVE-2026-27825 patch that only addressed downloads in v0.17.0. No authentication or user interaction is required beyond the ability to call the MCP tool.

Affected products

  • Atlassian MCP before fix

Identifiers

  • CVE-2026-77269
  • GHSA-h7wj-5v37-59r2
  • PYSEC-2026-4095

Timeline

  • 2026-09-22: disclosed: GHSA-h7wj-5v37-59r2 published
  • v0.17.0: other: Incomplete fix for CVE-2026-27825: validate_safe_path() added to downloads only

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.