← Back
CVE-2026-11529
medium
CVSS 6.3
Vulnerability in mysql-mcp-server (CVE-2026-11529)
Summary
vulnerability in mysql-mcp-server (CVE-2026-11529). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.3.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-11529** has been found in mysql-mcp-server.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: upgrade mysql-mcp-server to **0.3.0** or later.
If unsure, ask your IT team or search "mysql-mcp-server CVE-2026-11529" on the vendor's site.
CVE-2026-11529 (mysql-mcp-server) — CWE-74 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Patched: `0.3.0` — 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-74) exists in mysql-mcp-server.
📍 Affected scope
mysql-mcp-server — .
🔥 Severity
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.3.0**.
🛡️ 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-mcp-server' .` 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-mcp-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `mysql-mcp-server` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mysql-mcp-server to 0.3.0ステージング環境で 0.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
mysql-mcp-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.0"}]}]
References
- web https://github.com/designcomputer/mysql_mcp_server/commit/080bef9a96d625ce0dfbde573a08b93497871981
- web https://github.com/designcomputer/mysql_mcp_server/issues/89
- web https://github.com/designcomputer/mysql_mcp_server/pull/86
- web https://github.com/designcomputer/mysql_mcp_server/releases/tag/v0.3.0
- web https://vuldb.com/cve/CVE-2026-11529
- web https://vuldb.com/submit/836490
- web https://vuldb.com/vuln/369146
- web https://vuldb.com/vuln/369146/cti
- web https://nvd.nist.gov/vuln/detail/CVE-2026-11529
- web https://github.com/advisories/GHSA-mvq4-39wx-6h5g