Quick answers
- Is CVE-2026-14471 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14471 being exploited in the wild.
- How severe is CVE-2026-14471?
- High severity, with a CVSS score of 8.1, published 6 July 2026.
- Which products and versions are affected?
- Amazon Mcp-Gateway-Registry >=1.0.3, <=1.0.12.
- Is there a fix for CVE-2026-14471?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-14471 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-14471?
- Check whether you run Amazon AWS or Amazon Mcp-Gateway-Registry at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a SQL injection flaw in the retention policy subsystem of the metrics-service component within mcp-gateway-registry. The vulnerability exists in the handling of user-supplied input to retention policy configuration parameters, where input validation is insufficient or missing. An attacker must be authenticated to exploit this vulnerability, reducing the attack surface to valid users or compromised accounts. By crafting malicious SQL payloads in retention policy fields, an attacker can execute arbitrary SQL commands against the metrics database, potentially leading to unauthorized data access, modification, or deletion of metrics and monitoring data. Patches or updates from AWS should be applied to affected versions of mcp-gateway-registry.
Affected products
- AWS mcp-gateway-registry <UNKNOWN>
Timeline
- 2026-09-22: disclosed: CVE-2026-14471 publicly disclosed