Directory Traversal Affecting mcp-atlassian package, versions <0.22.1-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.48% (39th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-MCPATLASSIAN-18760707
  • published14 Aug 2026
  • disclosed12 Aug 2026

Introduced: 12 Aug 2026

CVE-2026-73498  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

Upgrade Chainguard mcp-atlassian to version 0.22.1-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream mcp-atlassian package and not the mcp-atlassian package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, confluence_upload_attachment passes its client-supplied file_path directly to open(file_path, "rb") in src/mcp_atlassian/confluence/attachments.py through _upload_attachment_direct() without calling validate_safe_path. An authenticated MCP client can read any file accessible to the server process and exfiltrate it to Confluence as an attachment. If an AI agent can be induced to call the tool through untrusted content, the same flaw can disclose server environment variables such as CONFLUENCE_API_TOKEN and other credentials. This issue is fixed in version 0.22.0.