VYPR
Medium severity4.3NVD Advisory· Published Jun 12, 2026

CVE-2026-44169

CVE-2026-44169

Description

MariaDB users with EXECUTE privilege via a role can view stored routine definitions without SHOW CREATE ROUTINE privilege, fixed in 11.4.11, 11.8.7, 12.3.2.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

MariaDB users with EXECUTE privilege via a role can view stored routine definitions without SHOW CREATE ROUTINE privilege, fixed in 11.4.11, 11.8.7, 12.3.2.

Vulnerability

In MariaDB server, a privilege check bypass exists in the handling of stored routine definitions. When a user is granted EXECUTE privilege on a stored routine via a role, they can view the routine's definition using SHOW CREATE PROCEDURE or SHOW CREATE FUNCTION even without the SHOW CREATE ROUTINE privilege [1][2]. This affects versions 11.4.1 to before 11.4.11, 11.8.1 to before 11.8.7, and 12.3.1 [2].

Exploitation

An attacker needs only a valid database account with the ability to be granted a role that has EXECUTE privilege on a stored routine. The attacker can then connect to the server, set the role, and execute SHOW CREATE PROCEDURE <routine_name> to retrieve the routine's source code [1]. No additional privileges are required.

Impact

The attacker gains unauthorized access to the stored routine's definition, which may contain sensitive business logic, credentials, or proprietary algorithms. This is a confidentiality breach, as the routine definition is normally protected by the SHOW CREATE ROUTINE privilege [2].

Mitigation

The issue has been patched in MariaDB versions 11.4.11, 11.8.7, and 12.3.2 [2]. Users should upgrade to these versions or later. As a workaround, administrators can avoid granting EXECUTE privilege via roles to untrusted users, or revoke the role from users who should not see routine definitions.

AI Insight generated on Jun 12, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

4

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

2

News mentions

0

No linked articles in our index yet.