CVE-2026-11529: SQL Injection in mysql-mcp-server — Upgrade to 0.3.0

Technical summary

The read_resource function in src/mysql_mcp_server/server.py fails to properly sanitize the uri_str argument before passing it to SQL operations. This classic SQL injection flaw (CWE-89) allows an authenticated attacker to inject malicious SQL syntax and execute unauthorized queries against the underlying MySQL database. The vulnerability is rooted in improper input validation (CWE-74) of user-controlled URI strings. Exploitation requires valid authentication credentials but no elevated privileges.

Business impact

Organizations using mysql-mcp-server are exposed to data exfiltration, unauthorized modification, and potential denial of service of critical database assets. The authenticated requirement limits blast radius to insider threats and compromised service accounts. However, if this component handles sensitive data (financial records, customer information, credentials), the impact could be severe. Unpatched systems face reputational damage and compliance violations if breaches occur.

Affected systems

designcomputer mysql-mcp-server versions 0.2.2 and earlier are affected. Version 0.3.0 and later contain the fix. Organizations should audit deployments to identify all instances of this component, including embedded or indirect dependencies in larger applications and services.

Exploitability

The vulnerability is exploitable by any user with valid authentication to the application. Public disclosure of the vulnerability means exploit techniques are likely documented or demonstrated. No sophisticated tooling is required—basic SQL injection payloads adapted to the URI parameter can trigger the flaw. The attack surface is moderate because exploitation requires prior authentication, but the low complexity of the attack increases likelihood of exploitation once discovered by threat actors.

Remediation

Immediately upgrade mysql-mcp-server to version 0.3.0 or later. Apply patch 080bef9a96d625ce0dfbde573a08b93497871981 if version upgrades are not immediately feasible. After patching, audit database logs for suspicious SQL activity dating back to deployment to detect prior exploitation. Reset or rotate credentials for service accounts that interact with the affected component.

Patch guidance

Verify that your deployment is running designcomputer mysql-mcp-server 0.3.0 or later using version reporting tools or dependency manifests. Test the upgrade in a staging environment to ensure compatibility with dependent applications. If internal patches are applied instead of upgrading, confirm that patch 080bef9a96d625ce0dfbde573a08b93497871981 is present in your codebase. Schedule patching within 30 days given the public disclosure and CVSS 6.3 severity.

Detection guidance

Monitor MySQL query logs for unusual SQL syntax in parameters originating from the mysql-mcp-server component—look for UNION, SELECT, OR 1=1, and other injection indicators. Track failed authentication attempts and subsequent successful queries from service accounts. Network detection should flag unexpected database connections or bulk data transfers from the affected service. Implement input validation alerts on URI parameters in application logs if available.

Why prioritize this

This vulnerability merits near-term attention despite MEDIUM severity (6.3 CVSS) because it combines authenticated SQL injection with public disclosure. The low attack complexity and authenticated-but-not-privileged requirement mean existing user accounts or compromised credentials pose immediate risk. Organizations dependent on database integrity should prioritize this above lower-complexity, lower-impact issues. However, it ranks below critical data-theft or unauthenticated RCE vulnerabilities.

Risk score, explained

CVSS 6.3 reflects a MEDIUM-severity issue: the network-accessible attack vector (AV:N) and low attack complexity (AC:L) increase score, but the requirement for prior login (PR:L) and lack of scope escalation (S:U) prevent a higher rating. The impact is partial across confidentiality, integrity, and availability (C:L, I:L, A:L), consistent with SQL injection that does not automatically compromise the entire system but allows data manipulation by an authenticated user. This score appropriately captures the moderate but meaningful risk posed by the flaw.

Frequently asked questions