← Back
CVE-2026-73498
high
CVSS 7.7
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**Path traversal** (CWE-22) exists in mcp-atlassian. Attackers reach the vulnerable code path via ``confluence_upload_attachment`` without authentication.
📍 Affected scope
mcp-atlassian — . Attack surface: `confluence_upload_attachment` / `file_path` / `CONFLUENCE_API_TOKEN`.
🔥 Severity
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.22.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mcp-atlassian to 0.22.0ステージング環境で 0.22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
mcp-atlassian
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.22.0"}]}]