<?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>Thu, 01 Oct 2026 23:57:55 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-77262</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-77262</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 accepts an attacker-controlled file_path and does not apply the path restriction added for the earlier download vulnerability. A caller can traverse outside the workspace and upload arbitrary server-readable files to Confluence. The advisory traces the vulnerable input and processing flow through confluence_upload_attachment, file_path, and CVE-2026-27825, 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 accepts an attacker-controlled file_path and does not apply the path restriction added for the earlier download vulnerability. A caller can traverse outside the workspace and upload arbitrary server-readable files to Confluence. The advisory traces the vulnerable input and processing flow through confluence_upload_attachment, file_path, and CVE-2026-27825, 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-77262</guid>
    </item>
    <item>
      <title>GHSA-p6hp-93wp-fh6p — MCP Atlassian: Path Traversal / Arbitrary File Read in confluence_upload_attachment MCP tool (incomplete fix of GHSA-xj…</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-p6hp-93wp-fh6p</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;`mcp-atlassian` exposes an MCP tool `confluence_upload_attachment` whose `file_path` argument is passed directly to `open(file_path, &amp;#34;rb&amp;#34;)` without any path validation. An attacker able to invoke the tool can read arbitrary files readable by the server process and exfiltrate them into a multipart upload directed at an attacker-controlled Confluence host. In the default `streamable-http` transport the server binds `0.0.0.0` with no built-in authentication, making this remotely exploitable without credentials.&lt;/p&gt;
&lt;p&gt;This is the **read-side symmetric twin** of GHSA-xjgw-4wvw-rgm4 / CVE-2026-27825 (fixed in v0.17.0). The v0.17.0 patch only covered the download/write path; the upload path that reads local files was left unguarded.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Vulnerable sink
`src/mcp_atlassian/confluence/attachments.py:477`
```python
with open(file_path, &amp;#34;rb&amp;#34;) as fp:
    files = {&amp;#34;file&amp;#34;: (filename, fp, content_type)}
    response = self.confluence.session.post(url, files=files, ...)
```
`file_path` is attacker-controlled end-to-end.&lt;/p&gt;
&lt;p&gt;### Taint source
`src/mcp_atlassian/servers/confluence.py:1290-1369`, tool definition at `:1307`:
```python
file_path: Annotated[str, Field(description=&amp;#34;Absolute path to the file to upload&amp;#34;)]
```
No Pydantic `pattern=`, no validator, no `validate_safe_path()` call.&lt;/p&gt;
&lt;p&gt;### Call chain
1. MCP client invokes `confluence_upload_attachment(page_id, file_path, ...)`
2. Server handler forwards to `ConfluenceFetcher.upload_attachment(file_path)`
3. `_upload_attachme…&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;`mcp-atlassian` exposes an MCP tool `confluence_upload_attachment` whose `file_path` argument is passed directly to `open(file_path, &amp;#34;rb&amp;#34;)` without any path validation. An attacker able to invoke the tool can read arbitrary files readable by the server process and exfiltrate them into a multipart upload directed at an attacker-controlled Confluence host. In the default `streamable-http` transport the server binds `0.0.0.0` with no built-in authentication, making this remotely exploitable without credentials.&lt;/p&gt;
&lt;p&gt;This is the **read-side symmetric twin** of GHSA-xjgw-4wvw-rgm4 / CVE-2026-27825 (fixed in v0.17.0). The v0.17.0 patch only covered the download/write path; the upload path that reads local files was left unguarded.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Vulnerable sink
`src/mcp_atlassian/confluence/attachments.py:477`
```python
with open(file_path, &amp;#34;rb&amp;#34;) as fp:
    files = {&amp;#34;file&amp;#34;: (filename, fp, content_type)}
    response = self.confluence.session.post(url, files=files, ...)
```
`file_path` is attacker-controlled end-to-end.&lt;/p&gt;
&lt;p&gt;### Taint source
`src/mcp_atlassian/servers/confluence.py:1290-1369`, tool definition at `:1307`:
```python
file_path: Annotated[str, Field(description=&amp;#34;Absolute path to the file to upload&amp;#34;)]
```
No Pydantic `pattern=`, no validator, no `validate_safe_path()` call.&lt;/p&gt;
&lt;p&gt;### Call chain
1. MCP client invokes `confluence_upload_attachment(page_id, file_path, ...)`
2. Server handler forwards to `ConfluenceFetcher.upload_attachment(file_path)`
3. `_upload_attachme…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-p6hp-93wp-fh6p</guid>
    </item>
    <item>
      <title>PYSEC-2026-4099 — MCP Atlassian: Path Traversal / Arbitrary File Read in confluence_upload_attachment MCP tool (incomplete fix of GHSA-xj…</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-4099</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;`mcp-atlassian` exposes an MCP tool `confluence_upload_attachment` whose `file_path` argument is passed directly to `open(file_path, &amp;#34;rb&amp;#34;)` without any path validation. An attacker able to invoke the tool can read arbitrary files readable by the server process and exfiltrate them into a multipart upload directed at an attacker-controlled Confluence host. In the default `streamable-http` transport the server binds `0.0.0.0` with no built-in authentication, making this remotely exploitable without credentials.&lt;/p&gt;
&lt;p&gt;This is the **read-side symmetric twin** of GHSA-xjgw-4wvw-rgm4 / CVE-2026-27825 (fixed in v0.17.0). The v0.17.0 patch only covered the download/write path; the upload path that reads local files was left unguarded.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Vulnerable sink
`src/mcp_atlassian/confluence/attachments.py:477`
```python
with open(file_path, &amp;#34;rb&amp;#34;) as fp:
    files = {&amp;#34;file&amp;#34;: (filename, fp, content_type)}
    response = self.confluence.session.post(url, files=files, ...)
```
`file_path` is attacker-controlled end-to-end.&lt;/p&gt;
&lt;p&gt;### Taint source
`src/mcp_atlassian/servers/confluence.py:1290-1369`, tool definition at `:1307`:
```python
file_path: Annotated[str, Field(description=&amp;#34;Absolute path to the file to upload&amp;#34;)]
```
No Pydantic `pattern=`, no validator, no `validate_safe_path()` call.&lt;/p&gt;
&lt;p&gt;### Call chain
1. MCP client invokes `confluence_upload_attachment(page_id, file_path, ...)`
2. Server handler forwards to `ConfluenceFetcher.upload_attachment(file_path)`
3. `_upload_attachme…&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;`mcp-atlassian` exposes an MCP tool `confluence_upload_attachment` whose `file_path` argument is passed directly to `open(file_path, &amp;#34;rb&amp;#34;)` without any path validation. An attacker able to invoke the tool can read arbitrary files readable by the server process and exfiltrate them into a multipart upload directed at an attacker-controlled Confluence host. In the default `streamable-http` transport the server binds `0.0.0.0` with no built-in authentication, making this remotely exploitable without credentials.&lt;/p&gt;
&lt;p&gt;This is the **read-side symmetric twin** of GHSA-xjgw-4wvw-rgm4 / CVE-2026-27825 (fixed in v0.17.0). The v0.17.0 patch only covered the download/write path; the upload path that reads local files was left unguarded.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Vulnerable sink
`src/mcp_atlassian/confluence/attachments.py:477`
```python
with open(file_path, &amp;#34;rb&amp;#34;) as fp:
    files = {&amp;#34;file&amp;#34;: (filename, fp, content_type)}
    response = self.confluence.session.post(url, files=files, ...)
```
`file_path` is attacker-controlled end-to-end.&lt;/p&gt;
&lt;p&gt;### Taint source
`src/mcp_atlassian/servers/confluence.py:1290-1369`, tool definition at `:1307`:
```python
file_path: Annotated[str, Field(description=&amp;#34;Absolute path to the file to upload&amp;#34;)]
```
No Pydantic `pattern=`, no validator, no `validate_safe_path()` call.&lt;/p&gt;
&lt;p&gt;### Call chain
1. MCP client invokes `confluence_upload_attachment(page_id, file_path, ...)`
2. Server handler forwards to `ConfluenceFetcher.upload_attachment(file_path)`
3. `_upload_attachme…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-4099</guid>
    </item>
  </channel>
</rss>
