Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61700 low CVSS 3.7

Vulnerability in org.mariadb.jdbc:mariadb-java-client (CVE-2026-61700)

Summary

Vulnerability in org.mariadb.jdbc:mariadb-java-client (CVE-2026-61700). Risk of unauthorized operations or information disclosure. Exploitable via allowLocalInfile. Mitigation: upgrade to 3.5.9 or later.

Original description

The description as published by the source.

Summary

MariaDB Connector/J does not enforce allowLocalInfile=false when
processing server-initiated LOCAL INFILE requests (protocol packet
type 0xfb). However, exploitation is constrained: the server can
only request the exact filename the client already included in its
LOAD DATA LOCAL INFILE query, it cannot redirect to arbitrary paths.

Details

When a client executes LOAD DATA LOCAL INFILE '/path/to/file', the
connector sends the filename to the server as part of the COM_QUERY.
A rogue or MitM server responds with a 0xfb packet echoing that
same filename. The connector, without checking allowLocalInfile,
transmits the file content.

The bypass is therefore limited to the file the application itself
intended to load. The attacker cannot escalate to other files
(e.g. /etc/passwd) unless the application's own query targets them.

The real-world risk is:

  • An application that uses LOAD DATA LOCAL INFILE on potentially
    sensitive files (credentials, exports, configs) and connects over
    an untrusted network.
  • allowLocalInfile=false is supposed to disable this entire
    mechanism as a defense-in-depth measure, but the flag is ignored.

Impact

The security guarantee of allowLocalInfile=false is not upheld,
but practical exploitation requires both a MitM/rogue server and an
application that actively uses LOCAL INFILE on sensitive data.

Credit

Reported by tharavel

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

CVE-2026-61700 (org.mariadb.jdbc:mariadb-java-client) — CWE-284 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: allowLocalInfile
Patched: 3.5.9 — 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-284) exists in org.mariadb.jdbc:mariadb-java-client. Attackers reach the vulnerable code path via allowLocalInfile without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.mariadb.jdbc:mariadb-java-client. Attack surface: allowLocalInfile.

🔥 Severity

Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.5.9.

🛡️ 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・依存マニフェストで org.mariadb.jdbc:mariadb-java-client を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.mariadb.jdbc:mariadb-java-client to 3.5.9

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

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

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

Affected packages

maven org.mariadb.jdbc:mariadb-java-client
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.9"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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