Skip to content
major vulnerability· requires attention

Widely-used Atlassian Confluence/Jira MCP server; critical RCE enabling full compromise.

Applications

CVE-2026-27825

9.0
Critical
EPSS 13%Patch availableMar 11, 2026

RCE in MCP server before 0.17.0 via unrestricted download_path.

common questions

Is CVE-2026-27825 being exploited?

Not confirmed. CVE-2026-27825 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 13% probability of exploitation in the next 30 days.

How severe is CVE-2026-27825?

CVE-2026-27825 is rated Critical with a CVSS score of 9.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-27825?

Yes. A fix has been recorded for CVE-2026-27825. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-27825 affect?

CVE-2026-27825 affects Atlassian Confluence MCP server (pre-0.17.0), Atlassian Jira MCP server (pre-0.17.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-27825?

Upgrade to MCP 0.17.0+.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Atlassian Confluence MCP server (pre-0.17.0)Atlassian Jira MCP server (pre-0.17.0)
impact

Attacker can write arbitrary content to any server-writeable path, enabling remote code execution (e.g., cron jobs) without restart.

action required

Immediate action required

affected versions
sooperset mcp-atlassian
  • affected< 0.17.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free