CVE-2026-85745

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th 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 — Patch released this week
4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.3Exploit: 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, ST_Area reads beyond the allocated buffer when processing invalid WKB for a MultiPolygon because the multi-polygon parser advances past a nested geometry header without first verifying enough input remains. A low-privileged remote attacker can supply malformed spatial data to disclose memory useful for bypassing ASLR as part of a multi-vulnerability chain. 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
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/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)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.3%
EPSS %ILE
25th
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 (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-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.3% within 30 daysSource: FIRST EPSS. 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 20, 2026

Advisory Details (9)

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

[MDEV-40328] ASAN error on malformed WKB multipolygon - Jira

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

Out-of-bound buffer read in ST_Area() of a MultiPolygon · 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-p7v9-24h4-mch8
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 2bf355e361db (MariaDB/server)

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

https://github.com/MariaDB/server/commit/2bf355e361db85153fdfba7b8a0f0d114d6a26ce

Vendor Advisories for CVE-2026-85745(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
redhatmariadb10-11-main-10.11.18-4.1.1.hum12026-10-19redhat
redhatmariadb11-8-main-11.8.9-0.1.hum12026-10-19redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 15× 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-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-20 15:47 UTCEG score recompute
  4. 2026-10-20 15:47 UTCVendor advisory
  5. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  6. 2026-10-19 13:31 UTCEG score recompute
  7. 2026-10-19 13:31 UTCVendor advisory
  8. 2026-10-19 12:58 UTCEG score recompute
  9. 2026-10-19 12:58 UTCVendor advisory
  10. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-18 03:05 UTCEG score recompute
  12. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-10-16 18:16 UTCEG score recompute
  14. 2026-10-16 16:38 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
  15. 2026-10-16 16:37 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-85745?
CVE-2026-85745 is a medium-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, ST_Area reads beyond the allocated buffer when processing invalid WKB for a MultiPolygon because the multi-polygon parser advances past a nested geometry header…
When was the CVE record for CVE-2026-85745 published?
The CVE record for CVE-2026-85745 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 20, 2026; the record at its source may have been updated since.
Is CVE-2026-85745 actively exploited?
CVE-2026-85745 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85745?
CVE-2026-85745 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-85745?
A fix for CVE-2026-85745 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-85745 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-85745

Explore →

Is Your Infrastructure Affected by CVE-2026-85745?

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

Book a Demo →Browse All CVEs