Which versions of MCP Gateway Registry are affected by EUVD-2026-41939?

Amazon's mcp-gateway-registry (versions before 1.0.13) contains a SQL injection vulnerability in its metrics service retention policy that permits arbitrary database queries, potentially exposing or…. A patch is available.

How to fix or mitigate EUVD-2026-41939?

Within 24 hours: Inventory all deployments of mcp-gateway-registry and verify current versions. Within 7 days: Test vendor patch v1.0.13 in staging to confirm compatibility and validate metrics functionality. Within 30 days: Deploy v1.0.13 to all production instances.

MCP Gateway Registry EUVD-2026-41939

Q: What is the CVSS score of EUVD-2026-41939?

EUVD-2026-41939 has a CVSS 4.0 base score of 8.6 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

| CVE-2026-14471 HIGH

SQL Injection (CWE-89)

2026-07-06 AMZN

SQLi AWS Mcp Gateway Registry

8.6

CVSS 4.0 · Vendor: AMZN

Severity by source

Vendor (AMZN) PRIMARY

8.6 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

8.1 HIGH

Remote authenticated user (PR:L, AV:N) with low complexity injects SQL yielding full read (C:H) and write (I:H) of the metrics store; no availability impact and scope unchanged.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (AMZN).

CVSS VectorVendor: AMZN

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jul 06, 2026 - 21:33 vuln.today

CVSS changed

Jul 06, 2026 - 21:22 NVD

8.1 (HIGH) 8.6 (HIGH)

DescriptionCVE.org

Improper Neutralization of Special Elements in the metrics-service retention policy management component in Amazon mcp-gateway-registry before 1.0.13 might allow an authenticated remote user to execute arbitrary SQL queries via a crafted table_name value that is interpolated into SQL statements in identifier position.

To remediate this issue, users should upgrade to version 1.0.13 or later.

AnalysisAI

SQL injection in the Amazon (agentic-community) mcp-gateway-registry before 1.0.13 allows an authenticated remote user to execute arbitrary SQL queries by supplying a crafted table_name that the metrics-service retention policy component interpolates directly into SQL in identifier position. Because the injection sits in an identifier (table name) position rather than a parameterizable value, it bypasses ordinary prepared-statement protections and grants broad read/write access to the metrics datastore. No public exploit identified at time of analysis, and the flaw is not on the CISA KEV list; a vendor patch (v1.0.13) is available.

Technical ContextAI

The mcp-gateway-registry is an open-source gateway and registry for Model Context Protocol (MCP) servers, maintained by the agentic-community and disclosed by Amazon (AMZN). The vulnerable code lives in the metrics-service retention policy management component, which purges or manages historical metrics rows by table. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command): a user-influenced table_name is concatenated into a SQL statement in an identifier position. Identifier-position injection is a well-known blind spot because parameter binding (?/$1 placeholders) only protects value positions, not table/column identifiers, so developers must whitelist or strictly escape identifiers - here that neutralization is missing, letting attacker-controlled special elements break out of the intended identifier.

RemediationAI

Vendor-released patch: 1.0.13 - upgrade the mcp-gateway-registry deployment to v1.0.13 or later (https://github.com/agentic-community/mcp-gateway-registry/releases/tag/v1.0.13), as documented in advisory GHSA-79qc-vqfr-xx5q and AWS bulletin 2026-052 (https://aws.amazon.com/security/security-bulletins/2026-052-aws/). If patching cannot be done immediately, restrict who holds authenticated access to the gateway and specifically the metrics-service/retention-policy management endpoints, since exploitation requires a valid account (PR:L); tightening account provisioning and applying least-privilege to the metrics-service database user (removing rights beyond the metrics tables) limits blast radius but does not close the injection. Monitoring metrics-service query logs for anomalous table_name values or unexpected SQL identifiers can provide detection, though it is a stopgap that does not prevent exploitation and adds log-volume overhead.