CVE•Published 2026-10-09•Modified 2026-10-14•1 article on news•5 live references•NVD data

CVE-2026-107818Mariadb · Mariadb

Vulnerability data via NVD (ingested)

CVSS v3.1

8.4

HIGH

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H

EPSS percentile

Exploit Prediction Scoring System · top 74% of all CVEs

Weaknesses (CWE)

CWE-15External Control of System or Configuration Setting

Description

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, the mariadb.service unit used /run/mysqld/wsrep-new-cluster during the next service restart. A database user with FILE privilege and a secure-file-priv configuration permitting writes to /run/mysqld could create that file and inject attacker-controlled environment values into the restarted service. 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.

Timeline

Published 2026-10-09

Modified 2026-10-14

External references

NVD MITRE Exploit-DB GitHub PoC VulnCheck

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

Shodan · vuln tag0 hosts

vuln:CVE-2026-107818

Hosts Shodan has explicitly fingerprinted as vulnerable.

Shodan · product

product:"Mariadb Mariadb"

All exposed Mariadb Mariadb instances — cross-reference with the CVE's affected-version range.

Shodan · banner/body mention

http.html:"Mariadb"

HTTP body or banner mentions "Mariadb" — catches deploys Shodan didn't identify as a product.

More intel sources (5)

Shodan report

vuln:CVE-2026-107818