dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-5059

CRITICAL · 9.8 CVSS v3.0 Published 2026-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
aws-mcp-server AWS CLI 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-27969.

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 confidence

Command injection vulnerability in aws-mcp-server's allowed commands list handling. The application fails to validate user-supplied strings before using them in system calls, allowing unauthenticated remote attackers to execute arbitrary code via crafted input to the MCP server.

MitigationImplement strict input validation and sanitization for all user-supplied command parameters; use parameterized execution methods instead of shell commands to prevent injection; apply principle of least privilege to 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if aws-mcp-server is installed
    Run 'npm list -g aws-mcp-server' or check for the binary in your PATH using 'which aws-mcp-server' or 'aws-mcp-server --version'
    Affected if The application is present and running in your environment
  2. Determine the installed version
    Execute 'aws-mcp-server --version' or check the package.json if running from source
    Affected if The version is any version of aws-mcp-server without the fix for command injection validation
  3. Verify allowed commands configuration exists
    Search configuration files for 'allowedCommands', 'allowed_commands', or similar settings in config files (e.g., ~/.aws/mcp.json, environment variables, or project config)
    Affected if The allowed commands feature is configured and user input can be passed to it
  4. Check for exposed MCP server network access
    Review network configuration to determine if the MCP server is listening on network interfaces (0.0.0.0) vs localhost only, and whether authentication is required
    Affected if The MCP server is accessible over the network without proper authentication
  5. Monitor for suspicious command execution patterns
    Review application logs and system process execution history for unusual commands or unexpected shell invocations originating from the MCP server process
    Affected if Logs show unexpected commands being executed or signs of injection attempts

You are affected if aws-mcp-server is running and the allowed commands feature processes user-supplied input without validation before executing system calls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization for all user-supplied command parameters; use parameterized execution methods instead of shell commands to prevent injection; apply principle of least privilege to the MCP server process.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5059 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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