CVE-2026-14471: SQL Injection in Amazon mcp-gateway-registry metrics-service

Technical summary

CVE-2026-14471 is a SQL injection flaw (CWE-89) in the metrics-service retention policy handler of mcp-gateway-registry. The component fails to properly neutralize special characters in the table_name parameter, allowing it to be interpolated directly into SQL identifier positions. This enables authenticated users to craft malicious input that breaks out of the intended SQL statement context and execute arbitrary queries. The vulnerability carries a CVSS v3.1 score of 8.1 (HIGH) with a vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, indicating network-accessible attack surface, low complexity, requirement for valid credentials, high confidentiality and integrity impact, and no availability impact.

Business impact

This vulnerability poses a direct threat to data confidentiality and integrity for organizations using mcp-gateway-registry. An insider or compromised account could exfiltrate sensitive metrics data, modify retention policies to hide audit trails, or corrupt the metrics database. While the CVSS score reflects HIGH severity, the authentication requirement limits blast radius—the risk is primarily from malicious insiders, credential compromise, or lateral movement by attackers with initial access. The impact compounds if metrics data is used for compliance reporting, cost allocation, or operational decision-making.

Affected systems

Amazon mcp-gateway-registry versions prior to 1.0.13 are vulnerable. The metrics-service retention policy management component is the specific attack surface. Organizations should inventory deployments of this component and determine which version they are running. The vulnerability does not appear to have widespread CISA KEV tracking, suggesting it may not yet be under active exploitation at scale.

Exploitability

Exploitation requires valid authentication credentials to the mcp-gateway-registry service. There is no indication of pre-authentication bypass or unauthenticated access. Once authenticated, an attacker can craft a table_name value containing SQL metacharacters or nested queries to execute arbitrary SQL. The low complexity (AC:L) and network accessibility (AV:N) mean that an attacker with credentials can exploit this without special conditions or tools. No public proof-of-concept or weaponized exploit has been identified in the KEV catalog.

Remediation

The primary remediation is to upgrade mcp-gateway-registry to version 1.0.13 or later. This version contains fixes to properly sanitize or parameterize table_name inputs before SQL execution. For organizations unable to upgrade immediately, implement network segmentation to restrict access to mcp-gateway-registry to trusted internal services, enforce strong credential management to reduce the risk of account compromise, and monitor database query logs for suspicious SQL patterns in the metrics-service component.

Patch guidance

Upgrade Amazon mcp-gateway-registry to version 1.0.13 or later. Verify the installed version in your deployment and test the upgrade in a non-production environment first to ensure no compatibility issues with dependent systems or retention policies. Consult the Amazon mcp-gateway-registry release notes to confirm the patch addresses CVE-2026-14471 and understand any breaking changes or configuration updates required.

Detection guidance

Monitor database query logs for unusual or malicious SQL patterns originating from the metrics-service component, such as UNION-based queries, nested subqueries, or attempts to access system tables. Audit authentication logs for mcp-gateway-registry access, particularly from service accounts or during off-hours. Check for unexpected changes to retention policies or metrics data. Implement Web Application Firewall (WAF) or database activity monitoring (DAM) rules to flag SQL injection signatures in table_name parameters if accessible through APIs.

Why prioritize this

CVE-2026-14471 merits HIGH priority because it enables both data exfiltration and modification by authenticated actors, affecting confidentiality and integrity simultaneously. However, the authentication requirement significantly reduces risk compared to pre-auth SQL injection vulnerabilities. Organizations with strong credential hygiene and limited internal access to mcp-gateway-registry should prioritize this lower than pre-auth critical flaws, but those with many service accounts, legacy access controls, or high-value metrics data should patch urgently.

Risk score, explained

The CVSS 8.1 (HIGH) score reflects the combination of network accessibility, low attack complexity, and high impact to confidentiality and integrity. The requirement for authentication (PR:L) prevents a full 9.0+ rating. No scope change means the impact is limited to the metrics-service and connected database, not lateral system compromise. Organizations must weigh this against their threat model: insider risk, credential distribution, and the criticality of metrics data in their architecture.

Frequently asked questions