Path Traversal in mcp-atlassian (CVE-2026-73498)
Summary
Path traversal in mcp-atlassian (CVE-2026-73498). Confidential information can be exposed externally. Exploitable via confluence_upload_attachment. Mitigation: upgrade to 0.22.0 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-73498 has been found in mcp-atlassian.
Attackers can target a specific entry point like confluence_upload_attachment over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade mcp-atlassian to 0.22.0 or later.
If unsure, ask your IT team or search "mcp-atlassian CVE-2026-73498" on the vendor's site.
CVE-2026-73498 (mcp-atlassian) — CWE-22 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: confluence_upload_attachment / file_path / CONFLUENCE_API_TOKEN
Patched: 0.22.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in mcp-atlassian. Attackers reach the vulnerable code path via confluence_upload_attachment.
Check the vendor advisory for the affected versions of mcp-atlassian. Attack surface: confluence_upload_attachment / file_path / CONFLUENCE_API_TOKEN.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 0.22.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mcp-atlassian' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mcp-atlassian' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mcp-atlassianを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mcp-atlassian to 0.22.0ステージング環境で 0.22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- patch github.com
- web github.com