Affects MariaDB, a widely used open-source database. Authenticated path-traversal can expose or corrupt table data—core infra risk across enterprises.
CVE-2026-102523
Authenticated path-traversal allows unauthorized table read/modify in MariaDB
Is CVE-2026-102523 being exploited?
Not confirmed. CVE-2026-102523 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-102523?
CVE-2026-102523 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-102523?
Yes. A fix has been recorded for CVE-2026-102523. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102523 affect?
CVE-2026-102523 affects MariaDB 10.11.1 - 10.11.18, MariaDB 11.4.0 - 11.4.12, MariaDB 11.8.0 - 11.8.8, MariaDB 12.3.0 - 12.3.2, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102523?
Upgrade to fixed versions or restrict DB user privileges immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users can craft partition names to traverse filesystem to read or modify other tables' files, enabling data theft or corruption.
Patch when possible
- affected>= 10.11.1 and < 10.11.19
- affected>= 11.4.1 and < 11.4.13
- affected>= 11.8.1 and < 11.8.9
- affected>= 12.3.1 and < 12.3.3
- affected>= 13.0.1 and < 13.0.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- none
- automatable
- no
- technical impact
- total
Assessed by CISA 5 Nov 2026 (SSVC 2.0.3).
timeline
- 5 Nov 2026Published
- 5 Nov 2026CISA SSVC assessment: exploitation none · same day later
- 5 Nov 2026CVE record last updated · same day later
- 6 Nov 2026Analysed by vulneraibility.com · same day later
also known as
- Linkgithub.com /MariaDB/server/security/advisories/GHSA-h4vr-wpff-jfx4
- Linkgithub.com /MariaDB/server/commit/98437c30ae52ed709f266e5f8095d779261a5879
- Linkgithub.com /MariaDB/server/releases/tag/mariadb-10.11.19
- Linkgithub.com /MariaDB/server/releases/tag/mariadb-11.4.13
- Linkgithub.com /MariaDB/server/releases/tag/mariadb-11.8.9
- Linkgithub.com /MariaDB/server/releases/tag/mariadb-12.3.3
- Linkgithub.com /MariaDB/server/releases/tag/mariadb-13.0.2
- Linkjira.mariadb.org /browse/MDEV-40413
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.