Is CVE-2026-11529 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-11529 being exploited in the wild.

How severe is CVE-2026-11529?

Medium severity, with a CVSS score of 6.3, published 8 June 2026.

Which products and versions are affected?

Design Computer Mysql-Mcp-Server <= 0.2.2; mysql-mcp-server (PyPI) ECOSYSTEM:introduced=0,fixed=0.3.0.

Is there a fix for CVE-2026-11529?

Yes. mysql-mcp-server (PyPI): upgrade to 0.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-11529 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-11529?

Check whether you run Design Computer Mysql-Mcp-Server or mysql-mcp-server (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-11529: designcomputer mysql-mcp-server SQL injection in read_resource

Q: Is there a fix for CVE-2026-11529?

Yes. mysql-mcp-server (PyPI): upgrade to 0.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-11529 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-11529?

Check whether you run Design Computer Mysql-Mcp-Server or mysql-mcp-server (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-11529 · Severity: medium · CVSS 6.3 · Published 2026-06-08

The MySQL MCP Server, a tool used for managing MySQL database connections via the Model Context Protocol, is vulnerable to SQL injection. An attacker with basic network access can send specially crafted requests that trick the server into executing unauthorized database commands. This could lead to the unauthorized viewing, modification, or deletion of sensitive data stored in the connected MySQL databases.

Technologies: Design Computer Mysql-Mcp-Server. Vendors: Design Computer, PyPI.

Quick answers

Is CVE-2026-11529 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-11529 being exploited in the wild.
How severe is CVE-2026-11529?: Medium severity, with a CVSS score of 6.3, published 8 June 2026.
Which products and versions are affected?: Design Computer Mysql-Mcp-Server <= 0.2.2; mysql-mcp-server (PyPI) ECOSYSTEM:introduced=0,fixed=0.3.0.
Is there a fix for CVE-2026-11529?: Yes. mysql-mcp-server (PyPI): upgrade to 0.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-11529 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-11529?: Check whether you run Design Computer Mysql-Mcp-Server or mysql-mcp-server (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

mysql-mcp-server (PyPI): upgrade to 0.3.0 or later
```
pip install "mysql-mcp-server>=0.3.0"
```

Technical details

A SQL injection vulnerability exists in mysql-mcp-server versions prior to 0.3.0. The flaw is located in the `read_resource` function within `src/mysql_mcp_server/server.py`, which fails to properly sanitize the `uri_str` argument used by the mysql URI handler. A remote attacker with low privileges can exploit this by providing a malicious URI string, leading to unauthorized database queries. The vulnerability has been patched in version 0.3.0 by improving input neutralization. Public exploit details have been disclosed.

Affected products

designcomputer mysql-mcp-server < 0.3.0

Identifiers

CVE-2026-11529
GHSA-mvq4-39wx-6h5g
PYSEC-2026-3579

Timeline

2026-06-08: disclosed
2026-06-08: advisory
2026-07-24: patched: GitHub advisory reviewed and updated with patch details.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.