Quick answers
- Is CVE-2026-107818 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107818 being exploited in the wild.
- How severe is CVE-2026-107818?
- High severity, with a CVSS score of 8.4, published 9 October 2026.
- Which products and versions are affected?
- Mariadb Server 10.6.1 to 10.6.27, 10.11.0 to 10.11.18, 11.4.0 to 11.4.12, 11.8.0 to 11.8.8, 12.3.0 to 12.3.2, 13.0.0 to 13.0.1.
- Is there a fix for CVE-2026-107818?
- Yes: fixed in 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107818 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-107818?
- Check whether you run Mariadb or Mariadb Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2
Technical details
A local privilege escalation vulnerability exists in MariaDB's systemd service file handling of wsrep (Galera cluster) bootstrap. An authenticated database user with FILE privilege can create a specially-crafted file at /run/mysqld/wsrep-new-cluster, which the service reads and uses to inject environment variables on restart. The vulnerability requires FILE privilege and a permissive secure-file-priv configuration.
Affected products
- MariaDB Server 10.6.1 to 10.6.27, 10.11.0 to 10.11.18, 11.4.0 to 11.4.12, 11.8.0 to 11.8.8, 12.3.0 to 12.3.2, 13.0.0 to 13.0.1
Timeline
- 2026-10-09: disclosed