CVE-2026-97380 json
MariaDB: GRANT PROXY with empty password incorrectly checks grantor's privileges
published 2026-09-07 2 mo ago modified 2026-10-28 11 d ago also BIT-mariadb-2026-97380 , BIT-mariadb-min-2026-97380 , BIT-mysql-client-2026-97380 , EUVD-2026-102924 , GHSA-625w-4hgq-qwmr
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
MariaDB server is a community developed fork of MySQL server. From 10.6.1 until 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2, the GRANT PROXY statement treats an IDENTIFIED clause with an empty password as though authentication were not specified, causing it to check the wrong grantor privileges. A low-privileged attacker who can name another account can exploit this authorization error to set that account's password. This issue is fixed in versions 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2.
Patch / fix
- bitnami mariadb 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2
- bitnami mariadb-min 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2
- bitnami mysql-client 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2
- mariadb mariadb 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2
- mariadb Debian 14 1:11.8.9+ds-1
debian advisories DEBIAN-CVE-2026-97380
- mariadb10.11 hummingbird 1 10.11.18-4.1.1.hum1
- mariadb10.11-pam hummingbird 1 10.11.18-4.1.1.hum1
- mariadb10.11-test hummingbird 1 10.11.18-4.1.1.hum1
- mariadb10.11-backup hummingbird 1 10.11.18-4.1.1.hum1
- mariadb10.11-common hummingbird 1 10.11.18-4.1.1.hum1
- mariadb10.11-errmsg hummingbird 1 10.11.18-4.1.1.hum1
- mariadb10.11-server hummingbird 1 10.11.18-4.1.1.hum1
- mariadb10.11-embedded hummingbird 1 10.11.18-4.1.1.hum1
red hat advisories RHSA-2026:84701RHSA-2026:84689
- mariadb openSUSE Tumbleweed 12.3.2-3.1
opensuse advisories openSUSE-SU-2026:12245-1
- github.com/MariaDB/server@dbd60d0 commit
- github.com/MariaDB/server/releases/tag/mariadb-10.11.19 release
- github.com/MariaDB/server/releases/tag/mariadb-10.6.28 release
- github.com/MariaDB/server/releases/tag/mariadb-11.4.13 release
- github.com/MariaDB/server/releases/tag/mariadb-11.8.9 release
- github.com/MariaDB/server/releases/tag/mariadb-12.3.3 release
- github.com/MariaDB/server/releases/tag/mariadb-13.0.2 release
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-97380 updated cvss 8.8
mariadb: mariadb: Privilege escalation via empty password in GRANT PROXY statement
-
Red Hat Enterprise Linux 7 mariadb, mariadb-libs, mariadb-test, mariadb-bench, mariadb-server, mariadb-embedded Red Hat Enterprise Linux 8 Judy, galera, mariadb, mariadb-pam, mariadb-test, mariadb-backup, +8 more Red Hat Enterprise Linux 9 mariadb, mariadb-pam, mariadb-test, mariadb-backup, mariadb-common, mariadb-errmsg, +6 more Red Hat Enterprise Linux 10 mariadb11.8 11.8.8-1.el10_2, mariadb10.11 10.11.18-1.el10_2 Red Hat OpenStack Platform 13 (Queens) mariadb, mariadb-libs, mariadb-test, mariadb-common, mariadb-config, mariadb-errmsg, +3 moreaffected: workaround, no fix available “Upgrade to the fixed version of MariaDB Server”
-
Red Hat Hardened Images mariadb11.8 11.8.9-0.1.hum1, mariadb11.8-pam 11.8.9-0.1.hum1, mariadb10.11 10.11.18-4.1.1.hum1, mariadb11.8-test 11.8.9-0.1.hum1, mariadb11.8-backup 11.8.9-0.1.hum1, mariadb11.8-common 11.8.9-0.1.hum1, +31 morefixed: vendor fix “Upgrade to the fixed version of MariaDB Server” RHSA-2026:84701
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 11 d ago
Exploit prediction
1.30% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mariadb | >=10.6.1, <10.6.28 >=10.11.0, <10.11.19 >=11.4.0, <11.4.13 >=11.8.0, <11.8.9 >=12.3.0, <12.3.3 >=13.0.0, <13.0.2 |
10.6.28 10.11.19 11.4.13 11.8.9 12.3.3 13.0.2 |
| bitnami | mariadb-min | >=10.6.1, <10.6.28 >=10.11.0, <10.11.19 >=11.4.0, <11.4.13 >=11.8.0, <11.8.9 >=12.3.0, <12.3.3 >=13.0.0, <13.0.2 |
10.6.28 10.11.19 11.4.13 11.8.9 12.3.3 13.0.2 |
| bitnami | mysql-client | >=10.6.1, <10.6.28 >=10.11.0, <10.11.19 >=11.4.0, <11.4.13 >=11.8.0, <11.8.9 >=12.3.0, <12.3.3 >=13.0.0, <13.0.2 |
10.6.28 10.11.19 11.4.13 11.8.9 12.3.3 13.0.2 |
Affected products
- MariaDB server
Classification
- Weakness
- Technology feeds
References
-
github.com
/MariaDB/server/commit/dbd60d0ad8daa2d01050346aa50b7b102490e456
patch
-
github.com
/MariaDB/server/security/advisories/GHSA-625w-4hgq-qwmr
vendor-advisory, advisory
-
github.com
/MariaDB/server/releases/tag/mariadb-10.11.19
release-notes, article
-
github.com
/MariaDB/server/releases/tag/mariadb-10.6.28
release-notes, article
-
github.com
/MariaDB/server/releases/tag/mariadb-11.4.13
release-notes, article
-
github.com
/MariaDB/server/releases/tag/mariadb-11.8.9
release-notes, article
-
github.com
/MariaDB/server/releases/tag/mariadb-12.3.3
release-notes, article
-
github.com
/MariaDB/server/releases/tag/mariadb-13.0.2
release-notes, article
-
jira.mariadb.org
/browse/MDEV-40470
issue-tracking, report
-
nvd.nist.gov
/vuln/detail/CVE-2026-97380
web
Sources
- CVE List CVE-2026-97380
- NVD CVE-2026-97380
- OSV BIT-mariadb-2026-97380
- OSV BIT-mariadb-min-2026-97380
- OSV BIT-mysql-client-2026-97380
- Maintainer advisory GHSA-625w-4hgq-qwmr
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of MariaDB/server published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.