Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

Command Injection RCE in aws-mcp-server

IdentifiersCVE-2026-5058CWE-78· Improper Neutralization of Special…

CVE-2026-5058 is an unauthenticated command injection vulnerability in aws-mcp-server. The flaw exists in the handling of the allowed commands list, where a user-supplied string is not properly validated before being used in a system call. Because attacker-controlled input can reach OS command execution logic without sufficient sanitization, a remote attacker can trigger arbitrary command execution on affected installations. Successful exploitation results in code execution in the security context of the MCP server process. The issue is tracked by the Zero Day Initiative as ZDI-26-246 and was previously tracked as ZDI-CAN-27968.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote, unauthenticated attacker to execute arbitrary operating system commands in the context of the aws-mcp-server process. Given the reported CVSS vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, the expected impact includes full compromise of confidentiality, integrity, and availability of the affected host within the privileges of the server process. This can enable host takeover, data theft, tampering, service disruption, and use of the compromised server as a pivot point for further intrusion.

Mitigation

If you can’t patch tonight, do this now.

Until a patch is available, do not expose aws-mcp-server to untrusted networks. Restrict access to trusted clients only using network segmentation, firewall rules, reverse-proxy ACLs, or bind the service only to localhost where feasible. Disable or avoid deployments that permit remote network access if operationally possible. Run the service with the minimum necessary OS and cloud privileges, isolate it in a hardened container or sandbox, and monitor for anomalous command execution from the server process. Because exploitation is unauthenticated, reducing reachability is the most important immediate mitigation.

Remediation

Patch, then assume compromise.

Apply a vendor fix when one becomes available. The underlying issue must be corrected by enforcing strict validation and sanitization of user-controlled input associated with the allowed commands list before any system call is made, and by avoiding shell-mediated command execution where possible. If maintaining the software internally, refactor command execution to use parameterized process invocation with a fixed command/argument allowlist rather than passing user-influenced strings to the shell. The provided content does not identify a patched version.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Amazon Web ServicesAws-Mcp-Serverapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.