CVE-2026-27825
A public proof of concept exists; no exploitation attested.
- Published2026-03-10
- Fixed in0.17.0
- WeaknessCWE-22 · CWE-73
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to version 0.17.0, the `confluence_download_attachment` MCP tool accepts a `download_path` parameter that is written to without any directory boundary enforcement. An attacker who can call this tool and supply or access a Confluence attachment with malicious content can write arbitrary content to any path the server process has write access to. Because the attacker controls both the write destination and the written content (via an uploaded Confluence attachment), this constitutes for arbitrary code execution (for example, writing a valid cron entry to `/etc/cron.d/` achieves code execution within one scheduler cycle with no server restart required). Version 0.17.0 fixes the issue.
Timeline
dates in UTC- 2026-03-1020:16CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-27825?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-27825?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.17 | < 0.17.0 | 0.17.0 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Mcp-atlassian mcp atlassian to 0.17.0
Advisories and patches
- github.comPatch
- github.comVendor Advisory
Detection
read 2026-10-23 19:25 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
Sources
- CISA-ADPSSVC decisionpoc2026-03-10
- OpenCVESSVC decisionpoc—
- CNACVSS 3.19read 2026-10-23
- NVDCVSS 3.18read 2026-10-23
- CNAweakness (CWE)CWE-22, CWE-73read 2026-10-23
- FIRST EPSSEPSS score1.5 %2026-10-22
- PoC-in-GitHubproof of concept1read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-03-10
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2026-27825?
Is CVE-2026-27825 actively exploited?
What is the CVSS score for CVE-2026-27825?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.