Skip to main content
CVE-2026-27825VulnerabilityPublished

CVE-2026-27825: sooperset mcp-atlassian · Path Traversal

Affects sooperset mcp-atlassianSource CVE Database V5

0

Not known to be exploited · 12% EPSS · CVSS 9.1 Critical : upgrade to 0.17.0 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
12.1% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.17.0
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade mcp-atlassian and sooperset/mcp-atlassian to 0.17.0.

Affected software

ProductAffectedFixed in
soopersetmcp-atlassianAffected
  • <0.17.0
Fixed in
  • 0.17.0
GitHubsooperset/mcp-atlassianpkg:github/sooperset/mcp-atlassianOther threatsAffected
  • <0.17.0
Fixed in
  • 0.17.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade MCP Atlassian to version 0.17.0 or later, where the vulnerability is fixed by enforcing directory boundary checks on the `download_path` parameter. Until the update can be applied, restrict access to the MCP Atlassian service to trusted users only and monitor for unusual file writes or cron job modifications on affected servers. Implement strict file system permissions to limit the MCP process’s write access to only necessary directories. Employ network segmentation and firewall rules to limit exposure of the MCP service. Conduct thorough audits of Confluence attachments and MCP logs for signs of exploitation attempts. Additionally, consider deploying host-based intrusion detection systems (HIDS) to detect unauthorized file modifications and anomalous cron entries. Educate administrators about the risks of path traversal vulnerabilities and ensure timely patch management processes are in place for all Atlassian-related components.

Description

MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to version 0.17.0, the `confluence_download_attachment` MCP tool accepts a `download_path` parameter that is written to without any directory boundary enforcement. An attacker who can call this tool and supply or access a Confluence attachment with malicious content can write arbitrary content to any path the server process has write access to. Because the attacker controls both the write destination and the written content (via an uploaded Confluence attachment), this constitutes for arbitrary code execution (for example, writing a valid cron entry to `/etc/cron.d/` achieves code execution within one scheduler cycle with no server restart required). Version 0.17.0 fixes the issue.

References

Community reviews

Loading reviews…