Vulnerability in mariadb (CVE-2026-35549)
Summary
Vulnerability in mariadb (CVE-2026-35549). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 11.4.10, 11.8.6, 12.2.2 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-35549 has been found in mariadb.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade mariadb to 11.4.10, 11.8.6, 12.2.2 or later.
If unsure, ask your IT team or search "mariadb CVE-2026-35549" on the vendor's site.
CVE-2026-35549 (mariadb) — CWE-789 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 11.4.10, 11.8.6, 12.2.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-789) exists in mariadb.
Check the vendor advisory for the affected versions of mariadb.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 11.4.10, 11.8.6, 12.2.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mariadb' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mariadb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mariadbを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mariadb to 11.4.10, 11.8.6, 12.2.2ステージング環境で 11.4.10, 11.8.6, 12.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-35549 mariadb Fixed in: 1:11.8.6-0+deb13u1
References
- report jira.mariadb.org
- web nvd.nist.gov