CVE-2026-5058
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 · uneditedaws-mcp-server Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of aws-mcp-server. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of the allowed commands list. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the MCP server. Was ZDI-CAN-27968.
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 · moderate confidenceThe vulnerability is a command injection flaw in aws-mcp-server's handling of the 'allowed commands list'. The application fails to properly validate user-supplied input before using it in a system call, allowing an unauthenticated remote attacker to execute arbitrary code in the context of the MCP server process.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify aws-mcp-server installationCheck for the aws-mcp-server binary or package on the system using commands like 'which aws-mcp-server', 'dpkg -l | grep aws-mcp-server', or 'rpm -qa | grep aws-mcp-server'Affected if The software is installed and running
-
Identify the installed versionRun 'aws-mcp-server --version' or check package manager metadata to determine the version numberAffected if The version is any version of aws-mcp-server (no specific version ranges provided)
-
Check for allowed commands configurationExamine configuration files for any 'allowed_commands', 'allowedlist', or similar settings that define permitted command lists. Look in default config locations or files specified in documentation.Affected if The allowed commands feature is configured with user-supplied input
-
Inspect command execution pathsReview the server configuration and code (if accessible) to see if user-supplied strings from the allowed list are passed directly to system call functions without validationAffected if User-provided command strings are used in system calls without sanitization
-
Check for signs of exploitationReview server logs, process logs, or audit logs for unusual command execution patterns, unexpected shell invocations, or suspicious arguments that may indicate command injection attemptsAffected if Logs show arbitrary command execution beyond expected behavior
A user is affected if aws-mcp-server is running with an allowed commands configuration that accepts user-supplied strings and passes them unsanitized to system calls.
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.
From vendor dataImplement strict input validation on the allowed commands list to ensure only whitelisted, safely-escaped commands are executed. Until a patch is available, restrict network access to the MCP server and consider network segmentation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5058 — 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-5058 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