sooperset mcp-atlassian up to 0.21.99 File Upload upload_attachment file_path path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.37+ |
Summary
A vulnerability identified as critical has been detected in sooperset mcp-atlassian up to 0.21.99. The impacted element is the function upload_attachment of the component File Upload. This manipulation of the argument file_path causes path traversal.
This vulnerability appears as CVE-2026-77260. The attack may be initiated remotely. There is no available exploit.
You should upgrade the affected component.
Details
A vulnerability has been found in sooperset mcp-atlassian up to 0.21.99 and classified as critical. Affected by this vulnerability is the function upload_attachment of the component File Upload. The manipulation of the argument file_path with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, the Confluence and Jira upload_attachment implementations accept an unconstrained file_path and open the referenced server-local file. A permitted MCP caller can upload sensitive host files to an Atlassian destination and then retrieve their contents. The advisory traces the vulnerable input and processing flow through upload_attachment, file_path, and CVE-2026-27825, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-77260 since 08/20/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
Upgrading to version 0.22.0 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 0.21.0
- 0.21.1
- 0.21.2
- 0.21.3
- 0.21.4
- 0.21.5
- 0.21.6
- 0.21.7
- 0.21.8
- 0.21.9
- 0.21.10
- 0.21.11
- 0.21.12
- 0.21.13
- 0.21.14
- 0.21.15
- 0.21.16
- 0.21.17
- 0.21.18
- 0.21.19
- 0.21.20
- 0.21.21
- 0.21.22
- 0.21.23
- 0.21.24
- 0.21.25
- 0.21.26
- 0.21.27
- 0.21.28
- 0.21.29
- 0.21.30
- 0.21.31
- 0.21.32
- 0.21.33
- 0.21.34
- 0.21.35
- 0.21.36
- 0.21.37
- 0.21.38
- 0.21.39
- 0.21.40
- 0.21.41
- 0.21.42
- 0.21.43
- 0.21.44
- 0.21.45
- 0.21.46
- 0.21.47
- 0.21.48
- 0.21.49
- 0.21.50
- 0.21.51
- 0.21.52
- 0.21.53
- 0.21.54
- 0.21.55
- 0.21.56
- 0.21.57
- 0.21.58
- 0.21.59
- 0.21.60
- 0.21.61
- 0.21.62
- 0.21.63
- 0.21.64
- 0.21.65
- 0.21.66
- 0.21.67
- 0.21.68
- 0.21.69
- 0.21.70
- 0.21.71
- 0.21.72
- 0.21.73
- 0.21.74
- 0.21.75
- 0.21.76
- 0.21.77
- 0.21.78
- 0.21.79
- 0.21.80
- 0.21.81
- 0.21.82
- 0.21.83
- 0.21.84
- 0.21.85
- 0.21.86
- 0.21.87
- 0.21.88
- 0.21.89
- 0.21.90
- 0.21.91
- 0.21.92
- 0.21.93
- 0.21.94
- 0.21.95
- 0.21.96
- 0.21.97
- 0.21.98
- 0.21.99
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Path traversalCWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: mcp-atlassian 0.22.0
Timeline
08/20/2026 CVE reserved09/22/2026 Advisory disclosed
09/22/2026 VulDB entry created
09/22/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-77260 (🔒)
GCVE (CVE): GCVE-0-2026-77260
GCVE (VulDB): GCVE-100-408613
Entry
Created: 09/22/2026 20:31Changes: 09/22/2026 20:31 (70)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.