CVE-2026-14471
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a SQL injection vulnerability in the metrics-service retention policy management component of Amazon mcp-gateway-registry. The issue occurs because user-supplied input for the table_name parameter is directly interpolated into SQL statements in identifier position (as a table name) rather than being properly parameterized or sanitized, allowing an authenticated attacker to inject arbitrary SQL commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Amazon mcp-gateway-registry installationLocate the mcp-gateway-registry service installation and determine its installed version by examining the service binary, container image tag, or deployment manifest version fieldAffected if The installed version is below 1.0.13
-
Verify metrics-service component is activeCheck the service configuration or runtime status to confirm the metrics-service component is enabled and runningAffected if metrics-service component is present and operational
-
Confirm retention policy management is accessibleInspect the exposed API endpoints or UI routes to verify the retention policy management functionality is available (typically under /metrics/retention or similar path)Affected if The retention policy management endpoint is exposed and accessible to authenticated users
-
Validate authentication is in placeReview the authentication configuration for the metrics-service to determine whether authentication is required for the vulnerable endpointAffected if The endpoint accepts authenticated requests (since an authenticated attacker is required)
User is affected if mcp-gateway-registry version is below 1.0.13, metrics-service with retention policy management is enabled, and the endpoint is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Amazon mcp-gateway-registry to version 1.0.13 or later to obtain the patched code that properly handles special elements in the table_name parameter.
version 1.0.13 or later
- 1. Identify the current version of Amazon mcp-gateway-registry deployed in your environment
- 2. Upgrade the mcp-gateway-registry service to version 1.0.13 or later
- 3. Verify the upgrade was successful by checking the installed version matches 1.0.13 or higher
- 4. Test that the metrics-service retention policy management functionality operates correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14471 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14471 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data