# CVE-2026-85788: Incomplete list of disallowed inputs in awslabs mysql-mcp-server

> Attackers can bypass read-only restrictions in the MySQL MCP Server to perform file read and write operations via SQL inline comments.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 9 Sep 2026

## What is CVE-2026-85788?

CVE-2026-85788 is a medium-severity vulnerability in AWS Labs MySQL MCP Server, published on 9 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Incomplete list of disallowed inputs in the mutable SQL detector component in Amazon awslabs mysql-mcp-server might allow context-dependent actors to bypass the read-only enforcement gate and reach file-read and file-write SQL sinks via SQL inline comments that the regex engine does not treat as whitespace.

To remediate this issue, users should upgrade to version 1.0.23.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2026-85788?


## How do I fix CVE-2026-85788?

No fix has been published for CVE-2026-85788 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85788 being exploited?

There is no known exploitation of CVE-2026-85788 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85788 and fix it if it is affected.

What it is: CVE-2026-85788 is a medium-severity vulnerability in AWS Labs MySQL MCP Server, published on 9 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-85788 in the wild and no public exploit code.

Affected product: AWS Labs MySQL MCP Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85788/ (Markdown: https://insights.sbomify.com/CVE-2026-85788/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85788
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85788
- OSV: https://osv.dev/vulnerability/CVE-2026-85788

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85788/
Summaries are generated and may contain mistakes; the official description above is the record.
