← Back
CVE-2026-27826
SSRF (Server-Side Request Forgery) in mcp-atlassian (CVE-2026-27826)
Summary
SSRF in mcp-atlassian (CVE-2026-27826). Confidential information can be exposed externally. Exploitable via `GET /rest/api/2/myself`. Mitigation: upgrade to `0.17.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-27826** has been found in mcp-atlassian.
Attackers can target a specific entry point like `GET /rest/api/2/myself` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade mcp-atlassian to **0.17.0** or later.
If unsure, ask your IT team or search "mcp-atlassian CVE-2026-27826" on the vendor's site.
CVE-2026-27826 (mcp-atlassian) — CWE-918 /
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: GET /rest/api/2/myself / Authorization header / `Authorization` / `JiraConfig`
Patched: `0.17.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
**SSRF** (CWE-918) exists in mcp-atlassian. Attackers reach the vulnerable code path via `GET /rest/api/2/myself` without authentication.
📍 Affected scope
mcp-atlassian — . Attack surface: GET /rest/api/2/myself / Authorization header / `Authorization` / `JiraConfig`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **0.17.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 `GET /rest/api/2/myself` requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /rest/api/2/myself' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /rest/api/2/myself` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade mcp-atlassian to 0.17.0ステージング環境で 0.17.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /rest/api/2/myself on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
mcp-atlassian
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.17.0"}]}]
References
- advisory https://github.com/advisories/GHSA-7r34-79r5-rcc9
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-27826
- package https://github.com/sooperset/mcp-atlassian
- package https://pypi.org/project/mcp-atlassian
- web https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-7r34-79r5-rcc9
- web https://github.com/sooperset/mcp-atlassian/commit/5cd697dfce9116ef330b8dc7a91291640e0528d9