CVE-2026-107814 — MariaDB: Insecure $HOME in MariaDB rpm packages
MariaDB server is a community developed fork of MySQL server. From 10.6.1 until 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2, MariaDB RPM packages created the dedicated mysql service account with the database data directory as its home directory. A database user with the FILE privilege could write startup dot-files such as .bash_profile into $HOME, and those files could execute when an administrator opened a login shell for the mysql account. Debian packages are not affected because they use /nonexistent as the account home. This issue is fixed in versions 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+3
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Mariadb Mariadb, MariaDB Server).
- Apply the fixed version or the patch documented under Remediation.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Mariadb | Mariadb | ≥ 10.6.1 and < 10.6.28≥ 10.11.1 and < 10.11.19≥ 11.4.1 and < 11.4.13≥ 11.8.1 and < 11.8.9≥ 12.3.1 and < 12.3.3≥ 13.0.1 and < 13.0.2 | Vulnerable | NIST National Vulnerability Database |
| MariaDB | Server | version >= 10.6.1, < 10.6.28version >= 10.11.1, < 10.11.19version >= 11.4.1, < 11.4.13version >= 11.8.1, < 11.8.9version >= 12.3.1, < 12.3.3version >= 13.0.1, < 13.0.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.4 | CVSS 3.1 | High | 1.7 | 6.0 | security-advisories@github.com via NIST National Vulnerability Database |
| 8.4 | CVSS 3.1 | High | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CWE-732 · Incorrect Permission Assignment for Critical Resource
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.28%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · mariadb/mariadb
- Source status changed · Undergoing Analysis → Analyzed
- Affected products added · mariadb/server
- SSVC assessment updated
- Source status changed · Awaiting Analysis → Undergoing Analysis
- Record published
- CVSS changed · 8.4
- Source status changed · → Awaiting Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- github.com/MariaDB/server/security/advisories/GHSA-m5gf-432r-g5jw
- github.com/MariaDB/server/commit/d842d6e994a8b0d67c280bf785a11357d6b316a2
- github.com/MariaDB/server/releases/tag/mariadb-12.3.3
- github.com/MariaDB/server/releases/tag/mariadb-11.4.13
- github.com/MariaDB/server/releases/tag/mariadb-10.6.28
- github.com/MariaDB/server/releases/tag/mariadb-11.8.9
- github.com/MariaDB/server/releases/tag/mariadb-13.0.2
- github.com/MariaDB/server/releases/tag/mariadb-10.11.19
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-97380 MariaDB: GRANT PROXY with empty password incorrectly checks grantor's privileges 1h
- Critical CVE-2026-92262 MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass. 1h
- High CVE-2026-86047 MariaDB: Insufficient quoting in mariadb-dump and SHOW commands 1h
- Medium CVE-2026-85745 MariaDB: Out-of-bound buffer read on in `ST_Area` of a multipolygon. 1h
- Critical CVE-2026-85746 MariaDB: Out-of-bound buffer write on in `ST_AsText` of nested GeometryCollections 1h
- Medium CVE-2026-85985 MariaDB: Unauthorized file access via CONNECT engine UDFs 1h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-107814 is "MariaDB: Insecure $HOME in MariaDB rpm packages", rated High. It affects Mariadb (Mariadb); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.4 describes technical severity. EPSS 0.28% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.