Skip to content
VulniPulse
Advisory severityHigh8.8Red Hat Linux

High [CVE-2026-97380] Privilege escalation via empty password in GRANT PROXY statement

This high-severity Red Hat Linux advisory covers CVE-2026-97380; related products: Red Hat Hardened Images, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-97380 Source published Source updated

VulniPulse record published Record updated

CVE-2026-97380
Related products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Get an email when Red Hat Linux RHEL & SELinux publishes the next one.

See Red Hat Linux RHEL & SELinux's last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat Linux RHEL & SELinux

Summary

Privilege escalation via empty password in GRANT PROXY statement. Red Hat rates this important (CVSS 8.8).

Weakness: CWE-266. Red Hat lists fixing advisory RHSA-2026:84689 with package mariadb11-8-main-11.8.9-0.1.hum1, mariadb10-11-main-10.11.18-4.1.1.hum1.

Affected products named by the advisory: Red Hat Hardened Images; Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8; and 4 more.

Affected products named by the advisory: Red Hat Enterprise Linux 9; Red Hat OpenStack Platform 13 (Queens); Red Hat package: mariadb10.11; Red Hat package: mariadb11.8.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 12 days ago·verify at source

Fixed versions
  • mariadb11-8-main-11.8.9-0.1.hum1
  • mariadb10-11-main-10.11.18-4.1.1.hum1
  • RHSA-2026:84689

Official advisory · high-confidence parse· fetched 12 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce strict grantor privilege checks when parsing GRANT PROXY statements containing empty authentication clauses in MariaDB: upgrade to mariadb 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2 (or the fixed Mariadb/Mariadb:10.11/Mariadb/Mariadb:10.3/Mariadb/Mariadb Devel:10.3/Mariadb/Mariadb:11.8/Mariadb builds), which check whether the auth pointer exists rather than checking string lengths in LEX_USER::has_auth() and remove extraneous USER_AUTH allocation in the parser, closing GRANT PROXY statement with empty IDENTIFIED password clause. Until patched, this is a concern on all MariaDB deployments allowing low-privileged authenticated database access, so use random and non-guessable database user account names and restrict access for untrusted database accounts. As a compensating measure, audit database account authorization changes to detect unauthorized modification of user passwords and proxy privileges, forward administrative SQL operations including GRANT PROXY to a SIEM for alerting on privilege escalation attempts, and alert on unexpected proxy privileges or role assignments to detect unauthorized account compromise. These controls limit blast radius and contain exploitation, but they do not fix the underlying improper authorization check defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1006 Privilege Change Audit Logging (medium)

Official advisory · high-confidence parse· fetched 12 days ago·verify at source

All Red Hat Linux advisories

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.