Critical SQL-execution flaw in cPanel affecting many hosting providers; can lead to widescale data compromise and account takeover.
CVE-2026-58048
cPanel flaw allows execution of arbitrary SQL as database root during database rename.
Is CVE-2026-58048 being exploited?
Not confirmed. CVE-2026-58048 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.97% probability of exploitation in the next 30 days.
How severe is CVE-2026-58048?
CVE-2026-58048 is rated Critical with a CVSS score of 9.4. 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-58048?
Not known from our data. No patch reference has been recorded for CVE-2026-58048, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-58048 affect?
CVE-2026-58048 affects cPanel (database rename functionality). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-58048?
Restrict/disable DB rename, tighten DB privileges, rotate root creds, apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Execute arbitrary SQL in DB root context → data exfiltration, schema/tables modification, account takeover.
Immediate action required
- affected< 11.110.0.137
- affected< 11.126.0.78
- affected< 11.134.0.48
- affected< 11.136.0.32
- affected< 11.137.9999.99
- affected< 11.118.0.71
- affected< 11.138.1.6
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.