Skip to main content

MCP Atlassian CVE-2026-77271

| EUVDEUVD-2026-84629 HIGH
Path Traversal (CWE-22)
2026-09-22 GitHub_M GHSA-6vmq-24h2-pj7j
8.3
CVSS 4.0 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain permitted MCP tool access
  2. Delivery
    Call Confluence attachment tool with traversal path
  3. Exploit
    Write malicious module into working directory
  4. Execution
    Application imports poisoned module
  5. Impact
    Execute arbitrary code in server process

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires mcp-atlassian < 0.22.0 where validate_safe_path defaults base_dir to os.getcwd() and the Confluence attachment call sites omit base_dir. The attacker must be a permitted MCP caller (PR:L) able to invoke the Confluence attachment/upload tool with a caller-supplied file_path, typically in a shared-credential or multi-tenant deployment. Code execution is NOT immediate: it is gated on the written file landing in the working-directory root as an importable module name AND the application subsequently importing (or re-importing) that module. Limiting factors: low-privilege tool access is still required (not fully unauthenticated), and successful code execution depends on an import of the overwritten module occurring after the write.

Impact

This is a genuine remote-exploitable code-execution path, but its real-world priority is moderated by preconditions. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N, VC:H/VI:N/VA:N/SC:H = 8.3) captures network reachability with low-privilege access and no user interaction, but the IMPACT mapping understates the flaw: an attacker-controlled write that overwrites an importable Python module yields arbitrary CODE EXECUTION, which should register as integrity and availability impact (VI:H/VA:H), not confidentiality-only. So the raw score is arguably conservative rather than inflated. Countervailing the severity: there is NO EPSS score, NO CISA KEV listing, and NO public exploit code identified at time of analysis - the primary evidence is the vendor security advisory (GHSA-6vmq-24h2-pj7j) and the fixing PR/commit. Exploitation is gated on a permitted caller reaching the Confluence attachment tool with shared/operator credentials (PR:L) AND the poisoned module actually being re-imported by the process, so this is targeted, config-dependent exploitation rather than mass-exploitable. Net: a real, patch-now issue for anyone running mcp-atlassian < 0.22.0 in a multi-tenant or shared-credential MCP deployment, but not a widespread wormable threat.

Exploit ScenarioDerived

A low-privileged but permitted client of a shared mcp-atlassian server invokes the Confluence upload_attachment tool with a crafted relative file_path that resolves inside the server's working directory, writing or overwriting a Python file that shadows an importable module. When the running application next imports that module, the attacker's code executes in the server process, bypassing the earlier CVE-2026-27825 remediation. No public PoC is currently identified, and the low attack complexity (AC:L) means the write itself is trivial once tool access is obtained.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 22, 2026

MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 lets a low-privileged authenticated MCP caller write attacker-chosen files into the server's working directory, because validate_safe_path defaults its base directory to os.getcwd() and the Confluence attachment call sites omit base_dir. Overwriting an importable Python module in that location can escalate to code execution once the application imports the modified module, and the vector intentionally bypasses the earlier remediation tracked as CVE-2026-27825. Exploitation requires permitted MCP tool access (CVSS vector shows PR:L, i.e. authenticated with low privileges) and a subsequent import or re-import of the overwritten module, so code execution is not immediate; no public exploit code has been identified at time of analysis and there is no CISA KEV entry. The vendor rates this 8.3, while an independent assessment confirms it is a genuine remote-exploitable code-execution path whose real-world priority is moderated by those preconditions.

RemediationAI

Vendor-released patch: upgrade to mcp-atlassian 0.22.0 or later (release tag v0.22.0; fix PR https://github.com/sooperset/mcp-atlassian/pull/1448, commit b041733473f95119dd539542a43c280737a8e460; advisory https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-6vmq-24h2-pj7j). Pin the dependency to >=0.22.0 and verify the running container/venv actually resolves that version, since CVE-2026-27825 remediation alone is bypassed here. Where immediate upgrade is impossible, use specific compensating controls: restrict which MCP clients and users may invoke the Confluence attachment upload and Jira attachment download tools (trade-off: legitimate attachment workflows are disabled for those callers); avoid shared-credential or multi-tenant deployments of the server so low-privileged callers cannot reach another tenant's workspace; and launch the server with a dedicated working directory that is not on Python's import search path (for example, run the code from an installed package rather than a checkout whose CWD is importable) and make that directory non-writable by the service account (trade-off: relative-path configuration and attachment workflows may need adjustment). Because the write is silent, monitor the server's working directory for unexpected .py or .pyc files and for module modifications as a detection proxy. No public exploit code has been identified at time of analysis, but the patch should not be deferred given the RCE escalation path and the bypass of the earlier CVE-2026-27825 fix.

Affected VersionsENISA

mcp-atlassian < 0.22.0

Affected Packages

pypi mcp-atlassian fix: 0.22.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in pypi

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

MCP Atlassian is a Python implementation of a Model Context Protocol (MCP) server that exposes Atlassian Confluence and Jira operations (attachment upload/download, search, etc.) as tools to MCP clients such as LLM agent frameworks. The flaw is a CWE-22 path-traversal / path-confinement weakness in the project's validate_safe_path helper: when a caller does not supply base_dir, the helper falls back to os.getcwd(), so 'safe' resolution is anchored to the process working directory rather than a dedicated workspace. The Confluence attachment upload call sites omit base_dir, so a tool argument (file_path/target path) can be resolved into the working-directory root. Because the working directory is where Python resolves imports first for many launch modes (via sys.path), a written file whose name matches a module the process later imports can be treated as the legitimate module, converting a constrained file write into arbitrary Python code execution. The source fix (PR #1448, commit b041733473f95119dd539542a43c280737a8e460, released as v0.22.0) confines the Confluence upload source to the validated workspace and makes the Jira download path refuse to write into the working-directory root at all, requiring an explicit subdirectory. The same patch set also bundles adjacent hardening, including ANDing (never replacing) the configured Confluence spaces allowlist in search and mounting SSRF redirect/DNS-pinning protections on the Confluence session. The CPE cpe:2.3:a:sooperset:mcp-atlassian:*:*:*:*:*:*:*:* confirms all package versions are in scope up to the fixed release.

Know when Mcp Atlassian gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 8.3 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
vuln.today AI 8.8 HIGH

Network-reachable tool call by a permitted low-privilege caller (PR:L, AV:N, AC:L) writes an importable module yielding full code execution, so C/I/A:H; process-scope so S:U.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Sep 22, 2026 - 19:02 EUVD
CVE Published
Sep 22, 2026 - 18:00 cve.org
HIGH 8.3

DescriptionCVE.org

MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, validate_safe_path defaults its base directory to os.getcwd(), and affected Confluence attachment call sites omit base_dir, allowing attacker-selected writes within the working directory. This Python module overwrite can provide code execution when the application later imports the modified module, bypassing the remediation tracked as CVE-2026-27825. This issue is fixed in version 0.22.0.

Technical POC Analysis

CWE-22 (path traversal), chaining to CWE-94 (code injection).

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

MCP Atlassian (sooperset/mcp-atlassian) versions prior to 0.22.0 allow an authenticated, low-privileged caller of the MCP interface to write attacker-controlled files into the server's working directory, which can escalate to code execution when the application later imports a modified module. Organizations running this Atlassian integration server - and the Confluence/Jira credentials it holds - are affected, since a compromised server process could expose connected collaboration platforms. Leadership should treat this as a high-priority patching item because exploitation requires only legitimate low-privilege access, even though no public exploit or active exploitation is currently known.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.6%
Top 52% exploitable
Prevalence
Low
niche open-source Python MCP server for Atlassian, developer/integration tooling
Threat Intel
1
1 source
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

63
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +42
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2026-77274 HIGH POC
8.8 Sep 22

Server-side request forgery in MCP Atlassian (the Model Context Protocol server for Confluence and Jira) prior to 0.22.0

CVE-2026-77243 HIGH POC
8.8 Sep 22

MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 applies its ENABLED_TOOLS and TOOLSETS least-privilege filters onl

CVE-2026-77262 HIGH POC
8.6 Sep 22

Path traversal in MCP Atlassian releases prior to 0.22.0 lets a caller of the confluence_upload_attachment MCP tool read

CVE-2026-77248 HIGH POC
8.6 Sep 22

Unauthenticated arbitrary file read in MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 lets a remote network calle

CVE-2026-77255 HIGH POC
8.6 Sep 22

Arbitrary local file read leading to data exfiltration affects sooperset's MCP Atlassian server (mcp-atlassian) prior to

CVE-2026-77246 HIGH POC
8.6 Sep 22

Unauthenticated server-local file exfiltration in MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 allows a remote

CVE-2026-77261 HIGH POC
8.5 Sep 22

Server-side request forgery in MCP Atlassian prior to 0.22.0 lets an attacker who controls or has already compromised th

CVE-2026-77267 HIGH POC
8.3 Sep 22

Server-side request forgery in MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 allows a low-privileged authenticat

CVE-2026-77257 HIGH POC
8.3 Sep 22

Arbitrary local file read in MCP Atlassian (mcp-atlassian) prior to 0.22.0 allows an authenticated MCP caller who can re

CVE-2026-77260 HIGH POC
8.3 Sep 22

Arbitrary server-local file read and exfiltration in MCP Atlassian (sooperset/mcp-atlassian) prior to 0.22.0 lets an aut

CVE-2026-77247 HIGH POC
8.3 Sep 22

Path traversal in the MCP Atlassian server (mcp-atlassian) prior to 0.22.0 allows an authenticated MCP client to read fi

CVE-2026-77251 HIGH POC
8.3 Sep 22

Information disclosure in MCP Atlassian (sooperset/mcp-atlassian) before 0.22.0 allows an authenticated caller of the MC

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy