<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 10:02:17 +0000</lastBuildDate>
    <item>
      <title>BREW-mcp-atlassian-CVE-2026-27825 — MCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in conflu…</title>
      <link>https://cve.radiocsirt.org/vuln/brew-mcp-atlassian-cve-2026-27825</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: mcp-atlassian&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: mcp-atlassian&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-mcp-atlassian-cve-2026-27825</guid>
    </item>
    <item>
      <title>EUVD-2026-275347</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-275347</link>
      <description>EUVD-2026-275347</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-275347</guid>
    </item>
    <item>
      <title>fkie_cve-2026-27825</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27825</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-27825</guid>
    </item>
    <item>
      <title>GHSA-xjgw-4wvw-rgm4 — MCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in conflu…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xjgw-4wvw-rgm4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mcp-atlassian&lt;/p&gt;
&lt;p&gt;### Summary
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).&lt;/p&gt;
&lt;p&gt;### Details
The tool parameter is defined in `src/mcp_atlassian/servers/confluence.py:~1275` without any path restriction:&lt;/p&gt;
&lt;p&gt;```python
  download_path: Annotated[
      str,
      Field(
          description=(
              &amp;#34;Full path where the file should be saved. Can be absolute or relative. &amp;#34;
              &amp;#34;Examples: &amp;#39;./downloads/report.pdf&amp;#39;, &amp;#39;/tmp/image.png&amp;#39;, &amp;#39;C:\\\\temp\\\\file.docx&amp;#39;. &amp;#34;
              &amp;#34;Parent directory will be created if it doesn&amp;#39;t exist.&amp;#34;
          )
      ),
  ],&lt;/p&gt;
&lt;p&gt;The implementation at src/mcp_atlassian/confluence/attachments.py:183–200:&lt;/p&gt;
&lt;p&gt;if not os.path.isabs(target_path):
      target_path = os.path.abspath(target_path)  # normalizes path, no restriction&lt;/p&gt;
&lt;p&gt;os.makedirs(os.path.dirname(target_path), exist_ok=True)  # creates any directory
  with open(target_path, &amp;#34;wb&amp;#34;) as f:                        # write…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mcp-atlassian&lt;/p&gt;
&lt;p&gt;### Summary
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).&lt;/p&gt;
&lt;p&gt;### Details
The tool parameter is defined in `src/mcp_atlassian/servers/confluence.py:~1275` without any path restriction:&lt;/p&gt;
&lt;p&gt;```python
  download_path: Annotated[
      str,
      Field(
          description=(
              &amp;#34;Full path where the file should be saved. Can be absolute or relative. &amp;#34;
              &amp;#34;Examples: &amp;#39;./downloads/report.pdf&amp;#39;, &amp;#39;/tmp/image.png&amp;#39;, &amp;#39;C:\\\\temp\\\\file.docx&amp;#39;. &amp;#34;
              &amp;#34;Parent directory will be created if it doesn&amp;#39;t exist.&amp;#34;
          )
      ),
  ],&lt;/p&gt;
&lt;p&gt;The implementation at src/mcp_atlassian/confluence/attachments.py:183–200:&lt;/p&gt;
&lt;p&gt;if not os.path.isabs(target_path):
      target_path = os.path.abspath(target_path)  # normalizes path, no restriction&lt;/p&gt;
&lt;p&gt;os.makedirs(os.path.dirname(target_path), exist_ok=True)  # creates any directory
  with open(target_path, &amp;#34;wb&amp;#34;) as f:                        # write…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xjgw-4wvw-rgm4</guid>
    </item>
    <item>
      <title>PYSEC-2026-408 — MCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in conflu…</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-408</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mcp-atlassian&lt;/p&gt;
&lt;p&gt;### Summary
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).&lt;/p&gt;
&lt;p&gt;### Details
 The tool parameter is defined in `src/mcp_atlassian/servers/confluence.py:~1275` without any path restriction:&lt;/p&gt;
&lt;p&gt;```python
  download_path: Annotated[
      str,
      Field(
          description=(
              &amp;#34;Full path where the file should be saved. Can be absolute or relative. &amp;#34;
              &amp;#34;Examples: &amp;#39;./downloads/report.pdf&amp;#39;, &amp;#39;/tmp/image.png&amp;#39;, &amp;#39;C:\\\\temp\\\\file.docx&amp;#39;. &amp;#34;
              &amp;#34;Parent directory will be created if it doesn&amp;#39;t exist.&amp;#34;
          )
      ),
  ],&lt;/p&gt;
&lt;p&gt;The implementation at src/mcp_atlassian/confluence/attachments.py:183–200:&lt;/p&gt;
&lt;p&gt;if not os.path.isabs(target_path):
      target_path = os.path.abspath(target_path)  # normalizes path, no restriction&lt;/p&gt;
&lt;p&gt;os.makedirs(os.path.dirname(target_path), exist_ok=True)  # creates any directory
  with open(target_path, &amp;#34;wb&amp;#34;) as f:                        # writ…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mcp-atlassian&lt;/p&gt;
&lt;p&gt;### Summary
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).&lt;/p&gt;
&lt;p&gt;### Details
 The tool parameter is defined in `src/mcp_atlassian/servers/confluence.py:~1275` without any path restriction:&lt;/p&gt;
&lt;p&gt;```python
  download_path: Annotated[
      str,
      Field(
          description=(
              &amp;#34;Full path where the file should be saved. Can be absolute or relative. &amp;#34;
              &amp;#34;Examples: &amp;#39;./downloads/report.pdf&amp;#39;, &amp;#39;/tmp/image.png&amp;#39;, &amp;#39;C:\\\\temp\\\\file.docx&amp;#39;. &amp;#34;
              &amp;#34;Parent directory will be created if it doesn&amp;#39;t exist.&amp;#34;
          )
      ),
  ],&lt;/p&gt;
&lt;p&gt;The implementation at src/mcp_atlassian/confluence/attachments.py:183–200:&lt;/p&gt;
&lt;p&gt;if not os.path.isabs(target_path):
      target_path = os.path.abspath(target_path)  # normalizes path, no restriction&lt;/p&gt;
&lt;p&gt;os.makedirs(os.path.dirname(target_path), exist_ok=True)  # creates any directory
  with open(target_path, &amp;#34;wb&amp;#34;) as f:                        # writ…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-408</guid>
    </item>
  </channel>
</rss>
