Path Traversal in mcp-atlassian (CVE-2026-77270)
Summary
Path traversal in mcp-atlassian (CVE-2026-77270). Confidential information can be exposed externally. Mitigation: upgrade to 0.22.0 or later.
Original description
The description as published by the source.
Summary
The upload attachment tools in both Confluence and Jira accept arbitrary file paths without path traversal validation. The upload_attachment methods read any file accessible to the server process and upload it to a Confluence page or Jira issue. Despite the existence of a validate_safe_path utility function (used correctly in download operations), the upload paths do not use it. This allows an authenticated MCP client (or an AI assistant manipulated via prompt injection) to exfiltrate arbitrary files from the server filesystem to an attacker-controlled Confluence page or Jira issue.
Details
The vulnerability exists in two parallel code paths:
Confluence: src/mcp_atlassian/confluence/attachments.py:35-108
# src/mcp_atlassian/confluence/attachments.py:62-65
# Convert to absolute path if relative
if not os.path.isabs(file_path):
file_path = os.path.abspath(file_path)
# Check if file exists
if not os.path.exists(file_path):
# error...
The file_path parameter is only checked for existence, not for path traversal. Any path like /etc/passwd, /etc/shadow, ~/.ssh/id_rsa, or ../../../sensitive-file is accepted.
Contrast with Confluence download operations (which ARE protected):
# src/mcp_atlassian/confluence/attachments.py:223
validate_safe_path(target_path) # <-- used for downloads
# src/mcp_atlassian/confluence/attachments.py:272
validate_safe_path(target_dir) # <-- used for downloads
The validate…
Source: NIST National Vulnerability Database 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-77270 has been found in mcp-atlassian.
Confidential information can be exposed externally. CVSS score: 6.5/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-77270" on the vendor's site.
CVE-2026-77270 (mcp-atlassian) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
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.
Check the vendor advisory for the affected versions of mcp-atlassian.
Severity: Medium (CVSS 6.5/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 nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web github.com