Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-77247 medium CVSS 6.5

Vulnerability in mcp-atlassian (CVE-2026-77247)

Summary

Vulnerability in mcp-atlassian (CVE-2026-77247). Confidential information can be exposed externally. Exploitable via stdio. Mitigation: upgrade to 0.22.0 or later.

Original description

The description as published by the source.

Summary

The Jira and Confluence attachment upload tools accept caller-controlled file path parameters and read those paths from the MCP server's local filesystem before uploading the file as an Atlassian attachment.

In local stdio deployments, this can expose files readable by the user's MCP process. In documented HTTP/SSE or streamable-http deployments, the impact is higher: any MCP client that is allowed to invoke write/upload tools can cause the server process to read a server-local file and upload it to Jira or Confluence.

This is not dependent on an AI prompt injection or model behavior. It can be triggered deterministically with a normal MCP tool call.

Details

The vulnerable behavior exists because upload tool arguments are treated as server-local filesystem paths.

Relevant implementation points:

  • mcp_atlassian.confluence.attachments.AttachmentsMixin.upload_attachment

    • Accepts file_path.
    • Converts the supplied value to an absolute path when needed.
    • Checks existence with os.path.exists.
    • Passes the path into the attachment upload flow.

  • mcp_atlassian.confluence.attachments.AttachmentsMixin._upload_attachment_direct

    • Opens the supplied file_path with open(file_path, "rb").
    • Sends the resulting file object as multipart form data to Confluence.

  • mcp_atlassian.confluence.attachments.AttachmentsMixin.upload_attachments

    • Iterates caller-supplied file_paths.
    • Calls upload_attachment for each path.

  • `mcp_atlassia…

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-77247 has been found in mcp-atlassian.
Attackers can target a specific entry point like stdio over the network to misuse the product.
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-77247" on the vendor's site.

CVE-2026-77247 (mcp-atlassian) — CWE-73 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: stdio / file_path / os.path.exists / file_paths
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

A vulnerability (CWE-73) exists in mcp-atlassian. Attackers reach the vulnerable code path via stdio.

📍 Affected scope

Check the vendor advisory for the affected versions of mcp-atlassian. Attack surface: stdio / file_path / os.path.exists / file_paths.

🔥 Severity

Severity: Medium (CVSS 6.5/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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'mcp-atlassian' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mcp-atlassian を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade mcp-atlassian to 0.22.0

    ステージング環境で 0.22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip mcp-atlassian
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.22.0"}]}]
PyPI mcp-atlassian
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.22.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details