Categories
CVE-2026-107818 high CVSS 8.4

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…

Summary

Vulnerability reported (CVE-2026-107818). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

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, the mariadb.service unit used /run/mysqld/wsrep-new-cluster during the next service restart. A database user with FILE privilege and a secure-file-priv configuration permitting writes to /run/mysqld could create that file and inject attacker-controlled environment values into the restarted service. 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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

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-107818 has been found.
Successful exploitation can lead to full system takeover. CVSS score: 8.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-107818" on the vendor's site.

CVE-2026-107818 — CWE-15 / CVSS v3 8.4
Attack vector: remote (network-reachable)
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.

❓ What is the problem

A vulnerability (CWE-15) has been reported.

📍 Affected scope

Check the vendor advisory for the affected versions.

🔥 Severity

Severity: High (CVSS 8.4/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami mariadb
[{"type":"SEMVER","events":[{"introduced":"10.6.1"},{"fixed":"10.6.28"},{"introduced":"10.11.1"},{"fixed":"10.11.19"},{"introduced":"11.4.1"},{"fixed":"11.4.13"},{"introduced":"11.8.1"},{"fixed":"11.8.9"},{"introduced":"12.3.1"},{"fixed":"12.3.3"},{"introduced":"13.0.1"},{"fixed":"13.0.2"}]}]
Bitnami mariadb-min
[{"type":"SEMVER","events":[{"introduced":"10.6.1"},{"fixed":"10.6.28"},{"introduced":"10.11.1"},{"fixed":"10.11.19"},{"introduced":"11.4.1"},{"fixed":"11.4.13"},{"introduced":"11.8.1"},{"fixed":"11.8.9"},{"introduced":"12.3.1"},{"fixed":"12.3.3"},{"introduced":"13.0.1"},{"fixed":"13.0.2"}]}]
Bitnami mysql-client
[{"type":"SEMVER","events":[{"introduced":"10.6.1"},{"fixed":"10.6.28"},{"introduced":"10.11.1"},{"fixed":"10.11.19"},{"introduced":"11.4.1"},{"fixed":"11.4.13"},{"introduced":"11.8.1"},{"fixed":"11.8.9"},{"introduced":"12.3.1"},{"fixed":"12.3.3"},{"introduced":"13.0.1"},{"fixed":"13.0.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details