CVE-2026-44169 | MariaDB: Authorization bypass in role-based routine-level privilege check exposes stored routine definitions

MariaDB server is a community developed fork of MySQL server. From versions 11.4.1 to before 11.4.11, 11.8.1 to before 11.8.7, and 12.3.1, a user getting EXECUTE access to a stored routine via a role, could see the routine definition even without SHOW CREATE ROUTINE privilege. This issue has been patched in versions 11.4.11, 11.8.7, and 12.3.2.

Published: 2026-06-12 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-44169 is rated Low Risk (24.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.28%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-44169

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.03% 0.28% +0.25%
2 2026-06-12 — 0.03% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-44169

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 [email protected]

Weakness enumeration for CVE-2026-44169

OS Trackers for CVE-2026-44169

vendor priority summary link
debian not yet assigned CVE-2026-44169 not yet assigned priority: Debian including 1 source packages (mariadb), 4 status rows across 4 suites (bookworm, forky, sid, trixie): open 3, resolved 1. https://security-tracker.debian.org/tracker/CVE-2026-44169
suse medium CVE-2026-44169 severity moderate: SUSE including 10 source package names (libmariadbd-devel-11.8.7-1.1, libmariadbd19-11.8.7-1.1, …), 10 product×package rows across 1 product lines (openSUSE Tumbleweed): Fixed 10. https://www.suse.com/security/cve/CVE-2026-44169/
ubuntu medium CVE-2026-44169 medium priority: Ubuntu including 5 source packages (mariadb, mariadb-10.0, mariadb-10.1, mariadb-10.3, mariadb-10.6), 27 status rows across 7 suites (bionic, focal, jammy, noble, questing, resolute, upstream): DNE 16, needs-triage 11. https://ubuntu.com/security/CVE-2026-44169

Affected software / configurations for CVE-2026-44169

Vendor Product Version Raw CPE
mariadb mariadb >= 11.4.1, < 11.4.11 cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*
mariadb mariadb >= 11.8.1, < 11.8.7 cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*
mariadb mariadb 12.3.1 cpe:2.3:a:mariadb:mariadb:12.3.1:*:*:*:*:*:*:*

References for CVE-2026-44169

cvelogic Threat Intelligence