Key points
- CVE-2026-14471 affects the metrics-service retention policy subsystem in mcp-gateway-registry.
- The vulnerability allows authenticated remote users to execute arbitrary SQL queries against the metrics database.
- Amazon released version 1.0.13 to address the issue; no workaround exists.
Amazon released version 1.0.13 of the open-source mcp-gateway-registry on July 6, 2026, to fix CVE-2026-14471. The update addresses an authenticated SQL injection flaw in the metrics-service retention policy subsystem. Systems running versions prior to 1.0.13 are exposed to this risk. There is no temporary workaround available.
In plain English
The flaw occurs because the software inserts a user-supplied table name directly into database commands without removing dangerous characters. An attacker who already has a login can trick the system into running their own code. This lets them read private data, such as API keys, or delete important records.
The background
The mcp-gateway-registry acts as a central hub for Model Context Protocol servers. It handles discovery and access control for AI agents using MCP tools. The vulnerability was found in the component that manages how long metric data is kept. Amazon rated the bulletin as important.
What changes now
The vendor confirmed that version 1.0.13 fixes the interpolation issue. Users must upgrade to this version or later to stop the attack. Teams with modified or forked versions of the code must apply the same corrections manually. Amazon advises checking the GitHub repository for the final release files.
Who needs to act first
Teams should prioritize environments exposed to external networks or untrusted internal users. Update systems that store sensitive API keys or critical operational metrics first. Test the update in a non-production environment to ensure compatibility before wider rollout. Back up database contents before applying changes. If immediate patching is impossible, restrict access to the metrics service to trusted administrative accounts only until the fix is deployed.
What to do and how to stay safe: AWS
- Check your current mcp-gateway-registry version against the released 1.0.13 update.
- Review access logs for unusual SQL queries or data retrieval attempts from authenticated users.
- Apply the vendor update to all production and development instances as soon as feasible.
- Monitor database integrity and audit trails for signs of unauthorized data modification or deletion.
Step-by-step guide: Emergency Patching: How to Fix Critical Flaws Without Breaking Systems
General security guidance from the Patch Review newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What specific vulnerability does this patch address?
The patch fixes CVE-2026-14471, an authenticated SQL injection flaw in the metrics-service retention policy subsystem.
Can an attacker exploit this without logging in?
No, the advisory states that an authenticated remote user is required to supply the crafted table name value.
Is there a way to mitigate the risk without updating?
No, the advisory explicitly states there is no workaround and recommends upgrading to version 1.0.13.
