Quick answers
- Is CVE-2026-97380 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97380 being exploited in the wild.
- How severe is CVE-2026-97380?
- High severity, with a CVSS score of 8.8, published 16 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-97380?
- Yes: fixed in MariaDB Server 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-97380 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-97380?
- Check whether you run 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: MariaDB Server 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2
Technical details
The GRANT PROXY statement incorrectly treats an empty password in an IDENTIFIED clause as if no authentication were specified, causing it to check the wrong set of grantor privileges. An attacker with database access can exploit this logic error to change passwords on arbitrary named accounts, bypassing the intended authorization checks. The fix distinguishes between "empty authentication specified" and "authentication not specified".
Affected products
- MariaDB 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-16: disclosed