AAK-MCP-GATEWAY-REGISTRY-CVE-2026-14471-001: Amazon mcp-gateway-registry below 1.0.13 (SQL injection)
- Severity
- HIGH
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/supply_chain.py- Auto-fixable
- No.
- SARIF name
McpGatewayRegistrySqlInjection
What it detects
The Amazon mcp-gateway-registry before 1.0.13 improperly neutralizes a caller-supplied table_name in the metrics-service retention-policy component: the value is interpolated directly into an SQL statement in identifier position, so an authenticated remote user can execute arbitrary SQL against the gateway's metrics store (CVE-2026-14471, HIGH CVSS 8.1, CWE-89, published 2026-07-06). A project that depends on the gateway registry at a version below 1.0.13 (or unpinned) is exposed.
How to fix
Upgrade mcp-gateway-registry to >= 1.0.13 and pin it explicitly. Never interpolate a request-supplied value into an SQL identifier position; validate table_name against a fixed allow-list of known table names, or quote it with the driver's identifier-quoting API rather than string formatting.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-GATEWAY-REGISTRY-CVE-2026-14471-001
Limitations
Reads the dependency declarations and launchers of the project root's requirements*.txt, pyproject.toml, Pipfile, package.json, .mcp.json, mcp.json, claude_desktop_config.json and *.mcp.yaml/.yml files, and reports one whose range admits a release below 1.0.13 or that states no version (a git requirement's dotted release tag is its version; a commit, a branch or a tag with no dot, @v2, states none), every agentic-community/mcp-gateway-registry git or image reference whose tag is below 1.0.13 or missing, a command line that runs mcp-gateway-registry without fetching it, and the version the root Pipfile.lock, poetry.lock, uv.lock or package-lock.json resolves when it is below 1.0.13. Only a tag written after the @ alone is read as a version: @refs/tags/v1.0.13, and the release an archive's file name states (.../archive/refs/tags/v1.0.13.tar.gz, mcp-gateway-registry-1.0.13.tar.gz), are not, so such a requirement is reported as unpinned even at 1.0.13 or later. A mention of the name that is none of these, such as a server's name or a URL, is not read, and neither is an image published under another name, such as the project's own public.ecr.aws/p3v1o3c6/registry. It does not read a sub-directory, including a requirements file there, .cursor/mcp.json or .vscode/mcp.json, or a pdm.lock, yarn.lock or pnpm-lock.yaml. A file over 2 MB is not read. A lockfile over 32 MiB is not read.
References
- CVE: CVE-2026-14471
- OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP05:2025 (Command Injection & Execution)
- OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-SUPPLY-01 (Runtime Package Fetch)
- CSA AI Controls Matrix (AICM): AIS-07, DSP-07
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-GATEWAY-REGISTRY-CVE-2026-14471-001.md: the page then shows that text, with the registry reference appended under it.