← Back
CVE-2026-3494
medium
CVSS 4.3
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-778) exists in Amazon mysql-client.
📍 Affected scope
Amazon mysql-client — .
🔥 Severity
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **10.6.25, 10.11.18, 12.0.2**.
🛡️ 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 'mysql-client' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mysql-client to 10.6.25, 10.11.18, 12.0.2ステージング環境で 10.6.25, 10.11.18, 12.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
mysql-client
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"10.6.25"},{"introduced":"10.7.0"},{"fixed":"10.11.18"},{"introduced":"11.0.0"},{"fixed":"12.0.2"}]}]
References
- AWS https://aws.amazon.com/security/security-bulletins/rss/2026-006-aws/
- web https://aws.amazon.com/security/security-bulletins/2026-006-AWS/
- web https://github.com/MariaDB/server/commit/635559a2ad68a5a6d1a354e8209c58323dba0261
- web https://github.com/aws/audit-plugin-for-mysql/commit/01e25a5cb1073f131eea774c06c8a056b1e4b2ff
- web https://nvd.nist.gov/vuln/detail/CVE-2026-3494