CVE-2026-44173: MariaDB: FILE privilege was not checked for subqueries in the FROM clause
MariaDB server is a community developed fork of MySQL server. From versions 10.6.1 to before 10.6.26, 10.11.1 to before 10.11.17, 11.4.1 to before 11.4.11, 11.8.1 to before 11.8.7, and 12.3.1, MariaDB allowed SELECT ... INTO OUTFILE and SELECT ... INTO DUMPFILE without verifying the FILE privilege if the FROM clause contained only subqueries. This issue has been patched in versions 10.6.26, 10.11.17, 11.4.11, 11.8.7, and 12.3.2.
Security readout for executives and security teams
Plain-English summary
This flaw lets a logged-in MariaDB user bypass the normal FILE privilege check in a specific query pattern. That can allow unauthorized server-side file writes through MariaDB. The business risk is high where applications or users have low-privilege database access on affected versions.
Executive priority
Treat as a high-priority database patching issue. Prioritize shared, externally reachable, or application-facing MariaDB servers because authenticated low-privilege access may be enough to cause serious integrity or availability impact.
Technical view
MariaDB Server 10.6.1-10.6.25, 10.11.1-10.11.16, 11.4.1-11.4.10, 11.8.1-11.8.6, and 12.3.1 mishandled FILE privilege validation for SELECT INTO OUTFILE/DUMPFILE when FROM contained only subqueries. CVSS is 8.1 with low privileges required.
Likely exposure
Exposure is likely for internet-facing or internally reachable MariaDB deployments running the listed versions, especially multi-tenant databases, shared application databases, or systems where untrusted users have database credentials.
Exploitation context
The source bundle does not show KEV listing or active exploitation evidence. Exploitation requires authenticated database access, but the vulnerable condition bypasses a privilege intended to prevent file-writing behavior.
Researcher notes
The key boundary failure is missing FILE privilege enforcement for OUTFILE/DUMPFILE when the FROM clause contains only subqueries. Evidence supports affected ranges, CVSS, and fixed versions, but not public exploitation status beyond KEV=false in the supplied bundle.
Mitigation direction
Upgrade MariaDB to 10.6.26, 10.11.17, 11.4.11, 11.8.7, or 12.3.2.
For Red Hat packages, apply the applicable RHSA advisory update.
Review MariaDB and distribution vendor guidance before relying on compensating controls.
Reduce unnecessary database accounts and privileges on affected instances.
Restrict database access paths to trusted applications and administrators.
Validation and detection
Inventory MariaDB Server versions across hosts, containers, and managed images.
Confirm each instance is outside the affected version ranges.
Check package status against the relevant Red Hat advisory if using Red Hat builds.
Review database users with low-privilege authenticated access to affected servers.
Where logs exist, review unusual SELECT INTO OUTFILE or DUMPFILE activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-266: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-266 · source CWE mapping
Incorrect Privilege Assignment
Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.