MariaDBDatabase / datastore
CVE-2026-44173
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMariaDB 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMariaDB had a privilege bypass vulnerability where SELECT ... INTO OUTFILE and SELECT ... INTO DUMPFILE statements did not properly verify the FILE privilege when the FROM clause contained only subqueries, allowing unauthorized file write operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
MariaDBDatabase / datastore
>= 10.6.1, < 10.6.26>= 10.11.1, < 10.11.17>= 11.4.1, < 11.4.11>= 11.8.1, < 11.8.7= 12.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check MariaDB server versionRun `mysql -V` from command line or execute `SELECT VERSION();` inside a MariaDB client sessionAffected if The version falls within any of these ranges: 10.6.1 to 10.6.25, 10.11.1 to 10.11.16, 11.4.1 to 11.4.10, 11.8.1 to 11.8.6, or exactly 12.3.1
-
Identify users granted FILE privilegeConnect to MariaDB and run: `SELECT user, host FROM mysql.user WHERE file_priv = 'Y';`Affected if Any users are listed with FILE privilege - those accounts could exploit the privilege bypass to write files to disk without proper authorization
-
Verify current FILE privilege enforcementCreate a test user without FILE privilege, grant only SELECT privilege, then attempt: `SELECT * INTO OUTFILE '/tmp/test.txt' FROM (SELECT 1 AS col) AS subq;` using that restricted userAffected if The statement succeeds and creates the file when it should fail, indicating the vulnerability is present
You are affected if your MariaDB version is in the affected ranges AND you have users with FILE privilege, as the bypass allows unauthorized file writes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.6.2610.11.1711.4.11
Upgrade MariaDB to patched versions (10.6.26+, 10.11.17+, 11.4.11+, 11.8.7+, or 12.3.2+) and review user FILE privilege assignments.
Upgrade to 10.6.26 (if on 10.6.x), 10.11.17 (if on 10.11.x), 11.4.11 (if on 11.4.x), 11.8.7 (if on 11.8.x), or 12.3.2 (if on 12.x)
- 1. Identify the currently installed MariaDB version using: `mysql --version` or `mariadb --version`
- 2. Determine which upgrade path applies based on your current version branch (10.6.x, 10.11.x, 11.4.x, or 11.8.x)
- 3. For RHEL/CentOS systems using yum: `sudo yum update MariaDB-server MariaDB-client`
- 4. For Debian/Ubuntu systems: `sudo apt-get update && sudo apt-get install mariadb-server mariadb-client`
- 5. For MariaDB YUM/DNF repository: `sudo dnf update MariaDB-server MariaDB-client`
- 6. After upgrade, restart the MariaDB service: `sudo systemctl restart mariadb` or `sudo systemctl restart mysqld`
- 7. Verify the new version is installed: `mysql --version`
- 8. Test that MariaDB starts and accepts connections normally
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MariaDB
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44173 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44173 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data