CVE-2026-16584
Raw vector
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-16584 is a high-severity Non-exit on Failed Initialization (CWE-455) vulnerability in Amazon (inferred from references). Its CVSS base score is 7.3 (High).
Operationally, ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
This vulnerability is AI-related — categorised as AI Agent Protocols and Integrations; in the Protocol-Specific Risks risk domain.
The strongest mitigations our analysis identified map to SC-24 (Fail in Known State) and SI-17 (Fail-safe Procedures) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-48299
Vulnerability Data
Improper handling of an initialization failure in AWS API MCP Server from 0.2.13 through 1.3.46 might allow an actor to bypass the user-configured security policy and execute AWS API operations that the policy was set to deny or gate. When…
more
initialization of the security policy enforcement data fails at server startup, the policy check is skipped for the lifetime of the process. IAM permissions on the configured credentials remain in effect and are unaffected. To remediate this issue, users should upgrade to version 1.3.47.
- CWE(s)
AI Security AnalysisAI
- AI Category
- AI Agent Protocols and Integrations
- Risk Domain
- Protocol-Specific Risks
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: mcp
Related Threats
Affected Assets
Mitigating Controls
Control response
—
—
—
V13.2.6V16.3.4
Mitigating Controls (NIST 800-53 r5) AI
SC-24 requires the system to fail to a known safe state on specified failures, directly stopping insecure continuation after bad initialization.
SI-17 mandates explicit fail-safe procedures on indicated failures, preventing the product from running in a degraded security posture after init errors.
CP-12 forces entry into a restricted safe mode when triggering conditions are detected, limiting exposure from failed security initialization.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-03 addresses only hardware lifecycle/replacement and has no effect on software initialization error-handling logic.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect missing exit-on-failure behavior during initialization.
Secure development lifecycle requires proper error handling and secure initialization, addressing the weakness.
Secure system architecture principles include fail-safe initialization and error handling requirements.
Secure coding practices mandate proper error handling during initialization to prevent insecure fallback states.
Change management may catch initialization configuration issues during deployment reviews.
Configuration management ensures secure initialization settings and failure handling, directly mitigating non-exit on failed init.