CVE-2026-16584

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.

CVSS v3 7.0 HIGH

7.0^/10

CVSS v3 : HIGH

Vector :

Exploitability : 1.0 / Impact : 5.9

Attack Vector LOCAL

Attack Complexity HIGH

Privileges Required NONE

User Interaction REQUIRED

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://aws.amazon.com/security/security-bulletins/2026-063-aws/
https://github.com/awslabs/mcp/security/advisories/GHSA-29w2-fq35-v728
https://pypi.org/project/awslabs.aws-api-mcp-server/1.3.47/

Configurations

No configuration.

History

24 Oct 2026, 13:10

Type	Values Removed	Values Added
Summary		(es) El manejo inadecuado de un fallo de inicialización en el servidor AWS API MCP desde la versión 0.2.13 hasta la 1.3.46 podría permitir a un actor eludir la política de seguridad configurada por el usuario y ejecutar operaciones de la API de AWS que la política estaba configurada para denegar o restringir. Cuando falla la inicialización de los datos de aplicación de la política de seguridad al inicio del servidor, la verificación de la política se omite durante la vida útil del proceso. Los permisos de IAM sobre las credenciales configuradas permanecen en vigor y no se ven afectados. Para solucionar este problema, los usuarios deben actualizar a la versión 1.3.47.

Information

Published : 2026-07-23 16:17

Updated : 2026-10-24 13:10

NVD link : CVE-2026-16584

Mitre link : CVE-2026-16584

CVE.ORG link : CVE-2026-16584

JSON object : View

Products Affected

No product.

CWE

CWE-455

Non-exit on Failed Initialization

{"id": "CVE-2026-16584", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-16584", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-07-23T18:16:30.277311Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "ff89ba41-3aa1-4d27-914a-91399e9639e5", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.0, "attackVector": "LOCAL", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 1.0}], "cvssMetricV40": [{"type": "Secondary", "source": "ff89ba41-3aa1-4d27-914a-91399e9639e5", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 7.3, "Automatable": "NOT_DEFINED", "attackVector": "LOCAL", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "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:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "PASSIVE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "ff89ba41-3aa1-4d27-914a-91399e9639e5", "affectedData": [{"vendor": "AWS", "product": "aws-api-mcp-server", "versions": [{"status": "affected", "version": "0.2.13", "lessThan": "1.3.47", "versionType": "custom"}], "defaultStatus": "unaffected"}]}], "published": "2026-07-23T16:17:15.787", "references": [{"url": "https://aws.amazon.com/security/security-bulletins/2026-063-aws/", "source": "ff89ba41-3aa1-4d27-914a-91399e9639e5"}, {"url": "https://github.com/awslabs/mcp/security/advisories/GHSA-29w2-fq35-v728", "source": "ff89ba41-3aa1-4d27-914a-91399e9639e5"}, {"url": "https://pypi.org/project/awslabs.aws-api-mcp-server/1.3.47/", "source": "ff89ba41-3aa1-4d27-914a-91399e9639e5"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "ff89ba41-3aa1-4d27-914a-91399e9639e5", "description": [{"lang": "en", "value": "CWE-455"}]}], "descriptions": [{"lang": "en", "value": "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.\n\n\n\nTo remediate this issue, users should upgrade to version 1.3.47."}, {"lang": "es", "value": "El manejo inadecuado de un fallo de inicializaci\u00f3n en el servidor AWS API MCP desde la versi\u00f3n 0.2.13 hasta la 1.3.46 podr\u00eda permitir a un actor eludir la pol\u00edtica de seguridad configurada por el usuario y ejecutar operaciones de la API de AWS que la pol\u00edtica estaba configurada para denegar o restringir. Cuando falla la inicializaci\u00f3n de los datos de aplicaci\u00f3n de la pol\u00edtica de seguridad al inicio del servidor, la verificaci\u00f3n de la pol\u00edtica se omite durante la vida \u00fatil del proceso. Los permisos de IAM sobre las credenciales configuradas permanecen en vigor y no se ven afectados.\n\nPara solucionar este problema, los usuarios deben actualizar a la versi\u00f3n 1.3.47."}], "lastModified": "2026-10-24T13:10:00.147", "sourceIdentifier": "ff89ba41-3aa1-4d27-914a-91399e9639e5"}