CVE-2026-16584: AWS API MCP Server security policy bypass via startup initialization failure
CVE-2026-16584 is verified against awslabs.aws-api-mcp-server · pip affected versions: >=0.2.13 and <1.3.47; equivalently 0.2.13 through 1.3.46. fixed version: 1.3.47, released on PyPI on 2026-07-22. This high reproduction includes runnable sandbox proof, artifacts, and a plain-text agent view under REPRO-2026-00303.
pruva-verify REPRO-2026-00303 curl -O https://pruva.dev/api/v1/reproductions/REPRO-2026-00303/artifacts/bundle/repro/reproduction_steps.sh && chmod +x reproduction_steps.sh && ./reproduction_steps.sh Primary-source research dossier for CVE-2026-16584 (AWS API MCP Server Security Policy Bypass via Startup Failure). AWS Security Bulletin 2026-063-AWS states that awslabs.aws-api-mcp-server versions >=0.2.13 and <1.3.47 load the read-operations index used by the optional security policy at startup; if initialization fails, the server continues running with per-request policy checks skipped for the lifetime of the process. In vulnerable versions, a configured denyList or elicitList can therefore be bypassed and denied/gated AWS CLI operations may reach the downstream AWS-call boundary even though policy would normally block them. The patched release 1.3.47 fails closed: the server refuses to start when the read-operations index cannot be loaded, and request-time execution is denied when the index is unavailable. Evidence sources: AWS bulletin 2026-063-AWS, PyPI 1.3.47 release page, and awslabs/mcp commit ab1bbebc097d674c1cdd4bd75a8f313be18473bf. Repo-scoped project: awslabs/mcp.
The agent's step-by-step process — every tool call, every handoff, the moment the exploit fired.
Loading session...
Scripts, logs, diffs, and output captured during the reproduction.