CVE-2026-35549

An issue was discovered in MariaDB Server before 11.4.10, 11.5.x through 11.8.x before 11.8.6, and 12.x before 12.2.2. If the caching_sha2_password authentication plugin is installed, and some user accounts are configured to use it, a large packet can crash the server because sha256_crypt_r uses alloca.

Published: 2026-04-03 Last update: 2026-06-02 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-35549 is rated Low Risk (31.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.05%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-35549

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-28 0.05% 0.05% +0.00%
2 2026-04-03 — 0.05% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-35549

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]

Weakness enumeration for CVE-2026-35549

OS Trackers for CVE-2026-35549

vendor priority summary link
debian unimportant CVE-2026-35549 unimportant priority: Debian including 1 source packages (mariadb), 4 status rows across 4 suites (bookworm, forky, sid, trixie): resolved 4. https://security-tracker.debian.org/tracker/CVE-2026-35549
redhat medium — https://access.redhat.com/security/cve/CVE-2026-35549
suse medium CVE-2026-35549 severity moderate: SUSE including 17 source package names (libmariadbd-devel, libmariadbd19, …), 98 product×package rows across 17 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS, … (17 product lines)): Known Not Affected 98. https://www.suse.com/security/cve/CVE-2026-35549/
ubuntu medium CVE-2026-35549 medium priority: Ubuntu including 5 source packages (mariadb, mariadb-10.0, mariadb-10.1, mariadb-10.3, mariadb-10.6), 23 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): DNE 12, needs-triage 10, released 1. https://ubuntu.com/security/CVE-2026-35549

Affected software / configurations for CVE-2026-35549

Vendor Product Version Raw CPE
mariadb mariadb < 11.4.10 cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*
mariadb mariadb >= 11.5.0, < 11.8.6 cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*
mariadb mariadb >= 12.0.0, < 12.2.2 cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*

References for CVE-2026-35549

cvelogic Threat Intelligence