cve.bz

CVE-2026-16584 aws aws-api-mcp-server: Non-exit on Failed Initialization

7.3 highEPSS 0.2%Fix available

High (7.3) in aws aws-api-mcp-server. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in awslabs-aws-api-mcp-server 1.3.47.

On this page
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 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.

Severity

CVSS 4.0

7.3 high
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

CVSS 3.1

7.0 high
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-16. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-07-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-455 Non-exit on Failed Initialization
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • awslabs-aws-api-mcp-server (PyPI): fixed in 1.3.47

Ask an AI about this CVE

Show the promptExplain CVE-2026-16584 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-16584?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-16584?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-16584 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
aws-api-mcp-serverfrom 0.2.13 before 1.3.47

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-29w2-fq35-v728PyPIawslabs-aws-api-mcp-server>=0.2.13 <1.3.471.3.47
PYSEC-2026-3549PyPIawslabs-aws-api-mcp-server>=0.2.13 <1.3.471.3.47

References

Check your stackJSON