CVE-2026-64639

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Incorrect database cloning process in Plesk from 18.0.52 before 18.0.79.6 and 18.0.80.2 allows a low-privileged user (customer, reseller) to execute arbitrary code on behalf of the database server administrator.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 14, 2026

References (1)

Vendor Advisories for CVE-2026-64639(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 61× in last 7d / 76× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 08:39 UTCGHSA enrichment
  2. 2026-08-21 04:56 UTCGHSA enrichment
  3. 2026-08-21 01:13 UTCEG score recompute
  4. 2026-08-21 01:13 UTCGHSA enrichment
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 21:31 UTCGHSA enrichment
  7. 2026-08-20 17:48 UTCGHSA enrichment
  8. 2026-08-20 14:05 UTCGHSA enrichment
  9. 2026-08-20 09:27 UTCGHSA enrichment
  10. 2026-08-20 05:45 UTCGHSA enrichment
  11. 2026-08-20 02:02 UTCGHSA enrichment
  12. 2026-08-19 22:19 UTCGHSA enrichment
  13. 2026-08-19 18:36 UTCEG score recompute
  14. 2026-08-19 18:36 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-19 14:10 UTCGHSA enrichment
  17. 2026-08-19 10:28 UTCGHSA enrichment
  18. 2026-08-19 06:45 UTCGHSA enrichment
  19. 2026-08-19 02:55 UTCGHSA enrichment
  20. 2026-08-18 22:47 UTCGHSA enrichment
  21. 2026-08-18 18:56 UTCGHSA enrichment
  22. 2026-08-18 15:13 UTCEG score recompute
  23. 2026-08-18 15:13 UTCGHSA enrichment
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-18 10:09 UTCGHSA enrichment
Show 51 more
  1. 2026-08-18 06:26 UTCGHSA enrichment
  2. 2026-08-18 02:42 UTCGHSA enrichment
  3. 2026-08-17 22:59 UTCGHSA enrichment
  4. 2026-08-17 19:14 UTCGHSA enrichment
  5. 2026-08-17 14:32 UTCEG score recompute
  6. 2026-08-17 14:32 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 10:49 UTCGHSA enrichment
  9. 2026-08-17 07:06 UTCGHSA enrichment
  10. 2026-08-17 03:24 UTCGHSA enrichment
  11. 2026-08-16 23:41 UTCGHSA enrichment
  12. 2026-08-16 19:58 UTCGHSA enrichment
  13. 2026-08-16 16:15 UTCEG score recompute
  14. 2026-08-16 16:15 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 12:32 UTCGHSA enrichment
  17. 2026-08-16 08:49 UTCGHSA enrichment
  18. 2026-08-16 05:07 UTCEG score recompute
  19. 2026-08-16 05:07 UTCGHSA enrichment
  20. 2026-08-16 01:24 UTCGHSA enrichment
  21. 2026-08-15 21:41 UTCGHSA enrichment
  22. 2026-08-15 17:58 UTCGHSA enrichment
  23. 2026-08-15 14:15 UTCGHSA enrichment
  24. 2026-08-15 10:32 UTCGHSA enrichment
  25. 2026-08-15 06:49 UTCGHSA enrichment
  26. 2026-08-15 03:02 UTCEG score recompute
  27. 2026-08-15 03:02 UTCGHSA enrichment
  28. 2026-08-15 01:30 UTCEPSS rescore
  29. 2026-08-14 23:19 UTCGHSA enrichment
  30. 2026-08-14 19:36 UTCEG score recompute
  31. 2026-08-14 19:36 UTCGHSA enrichment
  32. 2026-08-14 18:54 UTCEG score recompute
  33. 2026-08-14 18:54 UTCGHSA enrichment
  34. 2026-08-14 16:52 UTCGHSA enrichment
  35. 2026-08-14 13:06 UTCGHSA enrichment
  36. 2026-08-14 09:23 UTCGHSA enrichment
  37. 2026-08-14 05:41 UTCGHSA enrichment
  38. 2026-08-14 01:58 UTCGHSA enrichment
  39. 2026-08-13 22:16 UTCEG score recompute
  40. 2026-08-13 22:16 UTCGHSA enrichment
  41. 2026-08-13 22:00 UTCEPSS rescore
  42. 2026-08-13 18:33 UTCGHSA enrichment
  43. 2026-08-13 14:50 UTCGHSA enrichment
  44. 2026-08-13 11:07 UTCGHSA enrichment
  45. 2026-08-13 07:24 UTCGHSA enrichment
  46. 2026-08-13 03:41 UTCGHSA enrichment
  47. 2026-08-12 23:59 UTCGHSA enrichment
  48. 2026-08-12 20:16 UTCGHSA enrichment
  49. 2026-08-12 16:34 UTCEG score recompute
  50. 2026-08-12 15:36 UTCEG score recompute
  51. 2026-08-12 15:35 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64639?
CVE-2026-64639 is a critical vulnerability published on August 12, 2026. Incorrect database cloning process in Plesk from 18.0.52 before 18.0.79.6 and 18.0.80.2 allows a low-privileged user (customer, reseller) to execute arbitrary code on behalf of the database server administrator.
When was CVE-2026-64639 disclosed?
CVE-2026-64639 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64639 actively exploited?
CVE-2026-64639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.4% of all scored CVEs.
What is the CVSS score of CVE-2026-64639?
CVE-2026-64639 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-64639?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64639, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-64639

Explore →

Is Your Infrastructure Affected by CVE-2026-64639?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs