High-severity RCE/privilege escalation in Plesk, a widely used hosting control panel affecting many providers and customers; could disrupt hosted services.
CVE-2026-64639
Plesk DB-clone flaw allows low-privilege users to run code as database admin
Is CVE-2026-64639 being exploited?
Not confirmed. CVE-2026-64639 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 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-64639?
CVE-2026-64639 is rated Critical with a CVSS score of 9.3. 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-64639?
Yes. A fix has been recorded for CVE-2026-64639. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64639 affect?
CVE-2026-64639 affects Plesk >=18.0.52 and <18.0.79.6, Plesk 18.0.80.0 - 18.0.80.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64639?
Upgrade to 18.0.79.6 or 18.0.80.2+ and restrict DB-cloning privileges until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Low-privilege customer/reseller can execute arbitrary code as the database server administrator via incorrect DB cloning (privilege escalation/RCE).
Immediate action required
- affected>= 18.0.52 and < 18.0.79.6
- affected>= 18.0.80.0 and < 18.0.80.2
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.