Policy bypass via fail-open initialization
Published Jul 23, 2026 · Updated Jul 23, 2026
Security policy bypass in AWS API MCP Server 0.2.13 through 1.3.46 allows attackers to execute policy-denied AWS API operations. The main startup routine catches a get_read_only_operations failure, leaves READ_OPERATIONS_INDEX unset, and call_aws_helper omits check_security_policy when that index is absent. Exploitation requires a configured policy without fail-closed mode and a startup initialization failure; IAM permissions still bound executable operations.
Summary
What happened
Security policy bypass in AWS API MCP Server 0.2.13 through 1.3.46 allows attackers to execute policy-denied AWS API operations. The main startup routine catches a get_read_only_operations failure, leaves READ_OPERATIONS_INDEX unset, and call_aws_helper omits check_security_policy when that index is absent. Exploitation requires a configured policy without fail-closed mode and a startup initialization failure; IAM permissions still bound executable operations.
The record
- CVE
- CVE-2026-16584
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- Amazon Web Services
- Product
- AWS API MCP Server
- Classifications
- CWE-455, T1562.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2026CVE publishedPublication date reported by the CVE source.
- Jul 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.2.13 <1.3.47
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo