CVE-2026-107818

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-95919 (ENISA EUVD)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 9, 2026

Last Modified

October 14, 2026

Advisory Details (9)

Auto-updated Oct 9, 2026
Patch available. Sources: github, github_commit, github_release.
Web page

[MDEV-40629] environment injection via wsrep bootstrap in the service file - Jira

https://jira.mariadb.org/browse/MDEV-40629
GitHub release Patch Available

MariaDB Community Server 13.0.2

Patch available: MariaDB/server mariadb-13.0.2

https://github.com/MariaDB/server/releases/tag/mariadb-13.0.2
GitHub release Patch Available

MariaDB Community Server 12.3.3

Patch available: MariaDB/server mariadb-12.3.3

https://github.com/MariaDB/server/releases/tag/mariadb-12.3.3
GitHub release Patch Available

MariaDB Community Server 11.8.9

Patch available: MariaDB/server mariadb-11.8.9

https://github.com/MariaDB/server/releases/tag/mariadb-11.8.9
GitHub release Patch Available

MariaDB Community Server 11.4.13

Patch available: MariaDB/server mariadb-11.4.13

https://github.com/MariaDB/server/releases/tag/mariadb-11.4.13
GitHub release Patch Available

MariaDB Community Server 10.6.28

Patch available: MariaDB/server mariadb-10.6.28

https://github.com/MariaDB/server/releases/tag/mariadb-10.6.28
GitHub release Patch Available

MariaDB Community Server 10.11.19

Patch available: MariaDB/server mariadb-10.11.19

https://github.com/MariaDB/server/releases/tag/mariadb-10.11.19
GitHub commit Patch Available

commit e3d62d4e78fd (MariaDB/server)

Patch available: MariaDB/server mariadb-10.6.28 (contains commit e3d62d4e78fd)

https://github.com/MariaDB/server/commit/e3d62d4e78fd4941cef3f5053e6a50d0b32d740e
GitHub advisoryMentions a patch (unverified)

environment injection via wsrep bootstrap in the mariadb.service file · Advisory · MariaDB/server · GitHub

Affected: 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2.

https://github.com/MariaDB/server/security/advisories/GHSA-mhvc-vqcq-7vq5

Vendor Advisories for CVE-2026-107818(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatmariadb11-8-main-11.8.9-0.1.hum12026-10-19redhat
redhatmariadb10-11-main-10.11.18-4.1.hum12026-10-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb1:10.11.11-0+deb12u1 ... 1:11.8.9+ds-4 (57 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb1:11.8.2-1 ... 1:11.8.9+ds-4 (23 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb1:11.8.2-1 ... 1:11.8.8-1 (16 versions)
  • every version up to 1:11.8.9+ds-1: fixed in 1:11.8.9+ds-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-10-27 19:51 UTCEG score recompute
  7. 2026-10-27 19:51 UTCVendor advisory
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-10-25 14:54 UTCEG score recompute
  12. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-10-20 22:57 UTCEG score recompute
  17. 2026-10-20 22:57 UTCVendor advisory
  18. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-10-18 05:07 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
Show 14 more
  1. 2026-10-14 03:28 UTCEG score recompute
  2. 2026-10-14 02:23 UTCEG score recompute
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-10-12 16:38 UTCEG score recompute
  5. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-11 20:14 UTCEG score recompute
  7. 2026-10-11 18:17 UTCEG score recompute
  8. 2026-10-11 15:00 UTCEG score recompute
  9. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  10. 2026-10-11 06:20 UTCEG score recompute
  11. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-10-09 18:34 UTCEG score recompute
  13. 2026-10-09 17:34 UTCEG score recomputeFirst assessed: 8.4 HIGH
  14. 2026-10-09 17:33 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-107818?
CVE-2026-107818 is a high-severity vulnerability; its CVE record was published on October 9, 2026. 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…
When was the CVE record for CVE-2026-107818 published?
The CVE record for CVE-2026-107818 was published on October 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-107818 actively exploited?
CVE-2026-107818 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107818?
CVE-2026-107818 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107818?
A fix for CVE-2026-107818 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107818 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107818

Explore →

Is Your Infrastructure Affected by CVE-2026-107818?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs