Skip to main content
VulnerabilityPublished Updated

CVE-2026-35549: MariaDB Server

Affects mariadbSource GCVE Database

0
Compare
Authoritative record:CVE-2026-35549· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium · fixed in 12.2.2 : update mariadb when convenient.

Data as of 17 Nov 2026, 16:34 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (mitre)CVSS 3.16.5
Patch
Available – fixed in 12.2.2, 11.8.6, 11.4.10
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 3 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 16 Nov 2026.

What to do

Upgrade mariadb to 12.2.2, 11.8.6 or 11.4.10.

Affected software

ProductAffectedFixed in
Bitnamimariadbpkg:bitnami/mariadbOther threatsAffected
  • >=11.4.9 <11.4.10
  • >=11.8.4 <11.8.6
  • >=12.1.1 <12.2.2
Fixed in
  • 11.4.10
  • 11.8.6
  • 12.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches by upgrading to MariaDB Server versions 11.4.10, 11.8.6, or 12.2.2 or later. Since patches are available, updating to these fixed versions is the recommended remediation.

Description

A vulnerability in MariaDB Server versions before 11.4.10, 11.5.x through 11.8.x before 11.8.6, and 12.x before 12.2.2 allows a large packet to crash the server when the caching_sha2_password authentication plugin is used. This occurs because the sha256_crypt_r function uses alloca, which can lead to a server crash.

References

Community reviews

Loading reviews…