Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55854 medium CVSS 5.9

Vulnerability in mariadb (CVE-2026-55854)

Summary

Vulnerability in mariadb (CVE-2026-55854). Confidential information can be exposed externally. Mitigation: upgrade to 3.2.4 or later.

Original description

The description as published by the source.

Summary

When PAM (dialog) authentication is used, the connector can be coerced into sending the account password in cleartext over an insecure connection. A hostile or man-in-the-middle server can trigger this with the default configuration, disclosing the user's password.

Details

The mysql_clear_password plugin is gated behind a secure connection: the driver refuses to transmit the password in cleartext over plain TCP. The sibling PAM plugin handler (SendPamAuthPacketFactory, server-side plugin name dialog) did not override that gate and inherited the default value false, so it was not subject to the same secure-transport requirement.

As a result, a hostile or man-in-the-middle server can issue an Authentication Switch Request for the dialog plugin over plain TCP, and the driver responds with the user's password in cleartext. With the default configuration (sslMode=DISABLE, restrictedAuth=null) this is reachable with no non-default options.

Am I affected?

You are affected if all of the following hold:

You use mariadb Connector/Node.js at a version below the patched release(s).
Connections can occur over an insecure transport: plain TCP (sslMode=DISABLE), or a TLS mode that establishes server identity only via self-signed-certificate fingerprint validation.
An attacker can occupy an on-path (MITM) position, or otherwise cause the client to connect to a server they control, and present an Authentication Switch Request for the dialog plugin.

Connections over…

Source: GitHub Security Advisories (Global) 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-55854 has been found in mariadb.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade mariadb to 3.2.4 or later.
If unsure, ask your IT team or search "mariadb CVE-2026-55854" on the vendor's site.

CVE-2026-55854 (mariadb) — CWE-319 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.2.4 — 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.

❓ What is the problem

A vulnerability (CWE-319) exists in mariadb.

📍 Affected scope

Check the vendor advisory for the affected versions of mariadb.

🔥 Severity

Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.2.4.

🛡️ 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. 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

  1. 1
    Identify exposure identify 
    grep -r 'mariadb' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mariadb を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade mariadb to 3.2.4

    ステージング環境で 3.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

npm mariadb
[{"type":"SEMVER","events":[{"introduced":"3.5.0"},{"fixed":"3.5.3"}]}]
Bitnami mariadb
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.2.4"},{"introduced":"3.3.0"},{"fixed":"3.3.3"},{"introduced":"3.4.0"},{"fixed":"3.4.6"},{"introduced":"3.5.0"},{"fixed":"3.5.3"}]}]
Bitnami mariadb-min
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.2.4"},{"introduced":"3.3.0"},{"fixed":"3.3.3"},{"introduced":"3.4.0"},{"fixed":"3.4.6"},{"introduced":"3.5.0"},{"fixed":"3.5.3"}]}]
Bitnami mysql-client
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.2.4"},{"introduced":"3.3.0"},{"fixed":"3.3.3"},{"introduced":"3.4.0"},{"fixed":"3.4.6"},{"introduced":"3.5.0"},{"fixed":"3.5.3"}]}]

References

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