Vulnerability in Amazon mysql-client (CVE-2026-3494)
Summary
Vulnerability in Amazon mysql-client (CVE-2026-3494). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 10.6.25, 10.11.18, 12.0.2 or later.
Original description
The description as published by the source.
In MariaDB server version through 11.8.5, when server audit plugin is enabled with server_audit_events variable configured with QUERY_DCL, QUERY_DDL, or QUERY_DML filtering, if an authenticated database user invokes a SQL statement prefixed with double-hyphen (—) or hash (#) style comments, the statement is not logged.
Source: AWS Security Bulletins 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-3494 has been found in Amazon mysql-client.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade Amazon mysql-client to 10.6.25, 10.11.18, 12.0.2 or later.
If unsure, ask your IT team or search "Amazon mysql-client CVE-2026-3494" on the vendor's site.
CVE-2026-3494 (Amazon mysql-client) — CWE-778 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 10.6.25, 10.11.18, 12.0.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-778) exists in Amazon mysql-client.
Check the vendor advisory for the affected versions of Amazon mysql-client.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 10.6.25, 10.11.18, 12.0.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 'mysql-client' . 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 'mysql-client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mysql-clientを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Amazon mysql-client to 10.6.25, 10.11.18, 12.0.2ステージング環境で 10.6.25, 10.11.18, 12.0.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
- Alpine Linux ALPINE-CVE-2026-3494 mariadb Fixed in: 10.11.16-r0
- Debian DEBIAN-CVE-2026-3494 mariadb Fixed in: 1:10.11.18-0+deb12u1
- Ubuntu UBUNTU-CVE-2026-3494 mariadb-10.0
References
- advisory aws.amazon.com
- advisory nvd.nist.gov
- advisory github.com
- AWS aws.amazon.com
- patch github.com
- patch github.com