Skip to main content
CVE-2026-34303VulnerabilityPublished Updated

SUSE · Security update for mariadb

Affects SUSESource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-34303· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium · fixed in SUSE package updates : update SUSE when convenient.

Data as of 18 Nov 2026, 21:07 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 11.8.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Oracle CorporationMySQL ServerAffected
  • >=8.0.0 <=8.0.45
  • >=8.4.0 <=8.4.8
  • >=9.0.0 <=9.6.0
Fixed in–

AI-suggested

Apply the official MariaDB update to version 11.8.8 or later, which includes fixes for all listed vulnerabilities. No additional mitigation steps are indicated beyond applying this security update.

Description

This security update for MariaDB addresses multiple critical vulnerabilities in version 11.8.8. The fixes include issues such as audit plugin comment handling bypass, optimizer vulnerabilities, authentication plugin crashes, unsafe parameter handling in Galera SST processes, authorization bypasses exposing stored routine definitions, argument injection via unsanitized URLs on Windows, path traversal, incorrect string escaping, and privilege check failures. These vulnerabilities collectively pose significant risks to database integrity, confidentiality, and availability.

References

Community reviews

Loading reviews…