AWS patches authenticated SQL injection flaw in open-source mcp-gateway-registry

Amazon published a security bulletin on July 6, 2026, addressing CVE-2026-14471, an authenticated SQL injection vulnerability in its open-source mcp-gateway-registry. The flaw allows remote attackers to execute arbitrary SQL queries against the metrics database by supplying a crafted table name.

The vulnerability resides in the metrics-service retention policy management component. According to the advisory, the application interpolates caller-supplied table_name values into SQL statements without proper neutralization. This lack of sanitization enables authenticated users to read stored data, including API key material, and to delete or alter existing records.

Context and Background

The mcp-gateway-registry serves as an open-source gateway and registry for Model Context Protocol servers. It provides centralized discovery, authentication, and authorization services for AI agents. The product also handles the proxying of MCP tools, making it a critical infrastructure component for organizations deploying AI-driven workflows.

Amazon classified the bulletin as important and requiring attention. The company thanked the security research community for collaborating on this issue through the coordinated disclosure process. The advisory notes that the community worked with Amazon to handle the vulnerability responsibly before the public release.

Who is Affected

Any organization using the mcp-gateway-registry prior to version 1.0.13 is affected by this vulnerability. Because the flaw requires authentication, attackers must first obtain valid credentials to exploit the SQL injection vector. Once authenticated, however, the potential for data exfiltration and modification is significant, particularly regarding stored API keys.

There is no workaround for this vulnerability. Amazon explicitly stated that users must upgrade to version 1.0.13 or later to mitigate the risk. The advisory also urges maintainers of forked or derivative code to patch their versions to incorporate the new fixes provided in the official release.

What should you do?

Administrators should immediately check their current version of the mcp-gateway-registry against the vulnerable range. If running a version prior to 1.0.13, upgrade to the latest release as soon as possible. Monitor system logs for any suspicious SQL activity or unauthorized data access attempts from authenticated accounts.

What to do and how to stay safe: AWS

• Verify the current version of mcp-gateway-registry deployed in your environment.
• Upgrade to version 1.0.13 or later to apply the vendor-provided fix.
• Review access logs for authenticated users performing unusual database queries.
• Rotate any API keys or credentials stored in the metrics database if compromise is suspected.

Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is CVE-2026-14471?

It is an authenticated SQL injection vulnerability in the mcp-gateway-registry that allows arbitrary SQL execution.

Does this vulnerability require authentication?

Yes, an attacker must be an authenticated remote user to exploit the flaw.

Is there a workaround for this issue?

No, there is no workaround; users must upgrade to version 1.0.13 or later.