CVE-2026-92262

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.5% (73rd 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

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

9.9EG
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: 1.5%CVSS: 9.9Exploit: 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 #mysql50# bypass prefix is affected because it allows the #mysql50# prefix to bypass normal table-name filesystem encoding. An attacker can trigger the issue with a table name using the #mysql50# prefix, then use a #mysql50# table name to access files under their legacy unencoded name and cause crashes, data corruption, data exfiltration, or remote code execution. 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
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.5% × 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
1.5%
EPSS %ILE
73rd
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-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
1.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 16, 2026

Last Modified

October 21, 2026

Advisory Details (10)

Auto-updated Nov 6, 2026
Patch available. Sources: github, github_commit, github_release.
Web page

[MDEV-40362] #mysql50# mixes up with table names in the table cache and on disk - Jira

https://jira.mariadb.org/browse/MDEV-40362
GitHub advisoryMentions a patch (unverified)

Numerous issues caused by historical #mysql50# tablename encoding bypass · 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-65jj-h265-3m7h
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 f277eefa4248 (MariaDB/server)

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

https://github.com/MariaDB/server/commit/f277eefa424850a8cba5c2371406047f6395e8bb
GitHub commit Patch Available

commit 574ba66b2d6c (MariaDB/server)

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

https://github.com/MariaDB/server/commit/574ba66b2d6c5d71db83d416677876e9b592858e

Vendor Advisories for CVE-2026-92262(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatmariadb10-11-main-10.11.18-4.1.10.hum12026-10-29redhat

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 (58 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 13× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 22:56 UTCEchelonGraph re-scored
  2. 2026-11-12 16:35 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  3. 2026-11-11 20:54 UTCEchelonGraph re-scored
  4. 2026-11-11 20:54 UTCVendor advisory
  5. 2026-11-11 16:41 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  6. 2026-11-10 18:49 UTCEchelonGraph re-scored
  7. 2026-11-10 16:46 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  8. 2026-11-09 16:48 UTCEchelonGraph re-scored
  9. 2026-11-09 16:48 UTCVendor advisory
  10. 2026-11-09 16:36 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  11. 2026-11-08 16:41 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  12. 2026-11-08 14:46 UTCEchelonGraph re-scored
  13. 2026-11-08 14:46 UTCVendor advisory
  14. 2026-11-07 16:40 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  15. 2026-11-07 12:44 UTCEchelonGraph re-scored
  16. 2026-11-07 12:44 UTCVendor advisory
  17. 2026-11-06 21:55 UTCOSV refresh
  18. 2026-11-06 16:40 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  19. 2026-11-06 10:43 UTCEchelonGraph re-scored
  20. 2026-11-06 10:43 UTCVendor advisory
  21. 2026-11-05 16:39 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  22. 2026-11-05 08:42 UTCEchelonGraph re-scored
  23. 2026-11-05 08:42 UTCVendor advisory
  24. 2026-11-04 16:37 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  25. 2026-11-04 06:41 UTCEchelonGraph re-scored
Show 44 more
  1. 2026-11-04 06:41 UTCVendor advisory
  2. 2026-11-03 16:49 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  3. 2026-11-03 04:39 UTCEchelonGraph re-scored
  4. 2026-11-03 04:39 UTCVendor advisory
  5. 2026-11-02 16:46 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  6. 2026-11-02 02:31 UTCEchelonGraph re-scored
  7. 2026-11-02 02:31 UTCVendor advisory
  8. 2026-11-01 16:36 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  9. 2026-11-01 00:30 UTCEchelonGraph re-scored
  10. 2026-11-01 00:30 UTCVendor advisory
  11. 2026-10-31 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  12. 2026-10-30 22:29 UTCEchelonGraph re-scored
  13. 2026-10-30 16:35 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  14. 2026-10-29 20:28 UTCEchelonGraph re-scored
  15. 2026-10-29 16:34 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  16. 2026-10-28 18:26 UTCEchelonGraph re-scored
  17. 2026-10-28 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  18. 2026-10-27 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  19. 2026-10-27 16:18 UTCEchelonGraph re-scored
  20. 2026-10-26 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  21. 2026-10-26 14:07 UTCEchelonGraph re-scored
  22. 2026-10-25 16:34 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  23. 2026-10-25 13:50 UTCEchelonGraph re-scored
  24. 2026-10-25 11:38 UTCEchelonGraph re-scored
  25. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  26. 2026-10-24 09:36 UTCEchelonGraph re-scored
  27. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  28. 2026-10-23 07:34 UTCEchelonGraph re-scored
  29. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  30. 2026-10-22 05:29 UTCEchelonGraph re-scored
  31. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  32. 2026-10-21 03:27 UTCEchelonGraph re-scored
  33. 2026-10-21 02:33 UTCEchelonGraph re-scored
  34. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  35. 2026-10-20 00:37 UTCEchelonGraph re-scored
  36. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  37. 2026-10-18 22:35 UTCEchelonGraph re-scored
  38. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  39. 2026-10-18 03:00 UTCEchelonGraph re-scored
  40. 2026-10-17 20:32 UTCEchelonGraph re-scored
  41. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  42. 2026-10-16 17:28 UTCEchelonGraph re-scored
  43. 2026-10-16 16:38 UTCEchelonGraph re-scoredFirst assessed: 9.9 CRITICAL
  44. 2026-10-16 16:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92262?
CVE-2026-92262 is a critical-severity vulnerability; its CVE record was published on October 16, 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 #mysql50# bypass prefix is affected because it allows the #mysql50# prefix to bypass normal table-name filesystem encoding. An attacker can trigger the issue…
When was the CVE record for CVE-2026-92262 published?
The CVE record for CVE-2026-92262 was published on October 16, 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 21, 2026; the record at its source may have been updated since.
Is CVE-2026-92262 actively exploited?
CVE-2026-92262 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (73rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92262?
CVE-2026-92262 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92262?
A fix for CVE-2026-92262 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92262 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-92262

Explore →

Is Your Infrastructure Affected by CVE-2026-92262?

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