---
id: "GHSA-x25m-ph3m-3r9q"
kind: "vulnerability"
aliases: ["GHSA-x25m-ph3m-3r9q"]
title: "CVE-2026-85788 - Issue with awslabs mysql-mcp-server"
severity: "medium"
cvss: null
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "aws", "lab-disclosure", "mcp", "mysql", "python", "self-hosted"]
not_affected_if: ["not-using-mysql-mcp-server", "version-1.0.23-or-later"]
published_at: "2026-09-09T00:00:00+00:00"
first_seen_at: "2026-10-24T18:43:45+00:00"
updated_at: "2026-10-25T05:30:37+00:00"
sources: [{"source": "lab", "url": "https://aws.amazon.com/security/security-bulletins/rss/2026-103-aws/", "first_seen_at": "2026-10-24T18:43:45+00:00"}]
---

# CVE-2026-85788 - Issue with awslabs mysql-mcp-server

The awslabs mysql-mcp-server, a Model Context Protocol server for MySQL, could be tricked by SQL inline comments into running a statement its read-only check was meant to block. An attacker who can send queries through the server can write or change data the read-only mode was supposed to protect.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version with `pip show awslabs.mysql-mcp-server`; versions `1.0.21` and earlier are affected.
- Check whether the MySQL user configured for the server holds write or FILE privileges, for example with `SHOW GRANTS FOR 'mcp_user'@'%';`.

## Fix

- Upgrade to `awslabs.mysql-mcp-server` `1.0.23` or later with `pip install --upgrade awslabs.mysql-mcp-server`.
- Grant the MCP database user only the minimum privileges needed and do not give it the FILE privilege unless required.

## Timeline

- 2026-10-24T18:43:45+00:00 lab https://aws.amazon.com/security/security-bulletins/rss/2026-103-aws/ — AWS: CVE-2026-85788 - Issue with awslabs mysql-mcp-server

## Documents

- [advisory] AWS: CVE-2026-85788 - Issue with awslabs mysql-mcp-server https://aws.amazon.com/security/security-bulletins/rss/2026-103-aws/

## From the sources

CVE-2026-85788 - Issue with awslabs mysql-mcp-server

### CVE-2026-85788 - Issue with awslabs mysql-mcp-server

Bulletin ID: 2026-103-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 09/09/2026 09:15 PM PDT

Description:

We identified an issue in awslabs.mysql-mcp-server (an open-source, self-hosted Model Context Protocol server distributed via github.com/awslabs/mcp and PyPI). In affected versions, under certain conditions the read-only enforcement could be circumvented via SQL inline comments, allowing a statement to run that the read-only check was expected to block. The read-only mode provided by the server is a best-effort safeguard and is not a substitute for correctly scoped database permissions; the effective boundary is the permissions of the configured MySQL user.

This issue does not affect the confidentiality or integrity of any AWS service. awslabs.mysql-mcp-server is a client-side, self-managed package; customers control installation and the privileges of the database credentials they configure.

Affected versions: awslabs.mysql-mcp-server ≤ 1.0.21

Resolution:

The issue is addressed in awslabs.mysql-mcp-server 1.0.23. We recommend customers upgrade to 1.0.23 or later:

 pip install --upgrade awslabs.mysql-mcp-server

As defense in depth, ensure the database user configured for the MCP server is granted only the minimum privileges required, and does not hold the FILE privilege unless explicitly needed.

Workarounds:

None.

References:

- CVE-2026-85788
- GHSA-x25m-ph3m-3r9q

Acknowledgement:

We would like to thank Jaeyoung Yun for reporting this issue and working with us as part of our coordinated disclosure process.

 Please email aws-security@amazon.com with any security questions or concerns.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_