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

Vulnerability in mariadb (CVE-2026-107382)

Summary

Vulnerability in mariadb (CVE-2026-107382). Risk of unauthorized operations or information disclosure. Exploitable via Authentication.validateFingerPrint. Mitigation: upgrade to 3.5.4 or later.

Original description

The description as published by the source.

Description

On the zero-configuration TLS path, the connector accepts a self-signed server certificate at the TLS level and then validates the server's identity from the fingerprint hash the server appends to the final OK_Packet (Authentication.validateFingerPrint). That validation calls hash() on the authentication plugin in use to obtain the password-derived secret both sides combine with the seed and the certificate fingerprint.

Ed25519PasswordAuth.hash() referenced an identifier seed that was not in scope: it was neither a parameter of the method nor a module-scope binding, existing only as a parameter of the unrelated static encryptPassword(password, seed). Invoking the method therefore threw ReferenceError: seed is not defined.

The throw happens synchronously inside the socket data handler, and no frame between PacketInputStream.onData() and the plugin guards it, so the error escapes as an uncaught exception rather than surfacing as a connection error.

Because the fingerprint hash is what a legitimate MariaDB server sends on this path, ed25519 authentication with zero-configuration TLS never completed successfully — the failure is not limited to a hostile server.

Impact

Denial of service against the client process. Under Node's default uncaughtException behaviour the process exits, so a long-running service is terminated rather than seeing a failed connection attempt. No credential is disclosed and no data is altered; the impact is availabi…

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-107382 has been found in mariadb.
Attackers can target a specific entry point like Authentication.validateFingerPrint over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.9/10.
What to do: upgrade mariadb to 3.5.4 or later.
If unsure, ask your IT team or search "mariadb CVE-2026-107382" on the vendor's site.

CVE-2026-107382 (mariadb) — CWE-248 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Authentication.validateFingerPrint / seed / data / uncaughtException
Patched: 3.5.4 — apply immediately
Workaround: Provide the server certificate to the client (`ssl: { ca: ...
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-248) exists in mariadb. Attackers reach the vulnerable code path via Authentication.validateFingerPrint without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of mariadb. Attack surface: Authentication.validateFingerPrint / seed / data / uncaughtException.

🔥 Severity

Severity: Medium (CVSS 5.9/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.5.4.

🛡️ Workaround

Workaround: Provide the server certificate to the client (`ssl: { ca: ...

🔍 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 temporary workaround mitigate 
    Provide the server certificate to the client (`ssl: { ca: ...

    パッチが適用されるまでの応急処置として、Provide the server certificate to the client (`ssl: { ca: ... を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade mariadb to 3.5.4

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

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

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

Affected packages

npm mariadb
[{"type":"SEMVER","events":[{"introduced":"3.3.0"},{"fixed":"3.5.4"}]}]
Bitnami mariadb
[{"type":"SEMVER","events":[{"introduced":"3.3.0"},{"fixed":"3.5.4"}]}]
Bitnami mariadb-min
[{"type":"SEMVER","events":[{"introduced":"3.3.0"},{"fixed":"3.5.4"}]}]
Bitnami mysql-client
[{"type":"SEMVER","events":[{"introduced":"3.3.0"},{"fixed":"3.5.4"}]}]

References

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