CVE-2026-27826
Unauthenticated MCP server triggers requests to attacker URL; risk of IAM role theft in cloud.
Is CVE-2026-27826 being exploited?
Not confirmed. CVE-2026-27826 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 14% probability of exploitation in the next 30 days.
How severe is CVE-2026-27826?
CVE-2026-27826 is rated High with a CVSS score of 8.2. 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-27826?
Yes. A fix has been recorded for CVE-2026-27826. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-27826 affect?
CVE-2026-27826 affects Atlassian MCP server (Confluence/Jira). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-27826?
Upgrade to MCP 0.17.0+; restrict MCP endpoint; monitor outbound requests.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can force the MCP server to contact attacker URLs; cloud IAM role credentials via metadata; recon and content poisoning.
Patch when possible
- 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.