Privilege-escalation in a widely used database (MariaDB) with broad version impact and high CVSS; could affect many enterprises if exploited.
CVE-2026-107818
MariaDB privilege escalation via writable /run/mysqld/wsrep-new-cluster on service restart
Is CVE-2026-107818 being exploited?
Not confirmed. CVE-2026-107818 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.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-107818?
CVE-2026-107818 is rated High with a CVSS score of 8.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-107818?
Yes. A fix has been recorded for CVE-2026-107818. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-107818 affect?
CVE-2026-107818 affects MariaDB <10.6.28, MariaDB <10.11.19, MariaDB <11.4.13, MariaDB <11.8.9, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-107818?
Upgrade to listed fixed versions; revoke FILE privilege and restrict secure-file-priv.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local DB user with FILE privilege can inject environment into mariadb.service on restart, enabling privilege escalation or code execution as the service user.
Immediate action required
- affected>= 10.6.1 and < 10.6.28
- affected>= 10.11.1 and < 10.11.19
- affected>= 11.4.1 and < 11.4.13
- affected>= 11.8.1 and < 11.8.9
- affected>= 12.3.1 and < 12.3.3
- affected>= 13.0.1 and < 13.0.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.