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.
Original description
The description as published by the source.
A vulnerability was determined in designcomputer mysql-mcp-server up to 0.2.2. The impacted element is the function read_resource of the file src/mysql_mcp_server/server.py of the component mysql URI Handler. This manipulation of the argument uri_str causes sql injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. Upgrading to version 0.3.0 is sufficient to resolve this issue. Patch name: 080bef9a96d625ce0dfbde573a08b93497871981. Upgrading the affected component is advised.
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-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.
A vulnerability (CWE-74) exists in mysql-mcp-server.
Check the vendor advisory for the affected versions of mysql-mcp-server.
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.3.0.
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-mcp-server' . 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-mcp-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mysql-mcp-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mysql-mcp-server to 0.3.0ステージング環境で 0.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- patch github.com
- patch github.com
- report github.com
- report vuldb.com