awslabs.aws-api-mcp-server
Open source MCP Servers for AWS
View on Github
Activity
- Latest release
- 5d ago
- Total releases
- 96
- Cadence
- ~3 days
- Last 12 months
- 72
Reach
- Stars
- 9.7k
Details
- License
- Apache-2.0
- First release
- Jul 14, 2025
| Version | Released | |
|---|---|---|
1.5.5
patch
| ||
1.5.4
patch
| ||
1.5.3
patch
| ||
1.5.2
patch
| ||
1.5.1
patch
| ||
1.5.0
minor
| ||
1.4.2
patch
| ||
1.4.1
patch
| ||
1.4.0
minor
| ||
1.3.47
patch
| ||
1.3.46
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.45
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.44
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.43
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.42
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.41
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.40
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.39
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.38
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.37
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.36
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.35
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.34
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.33
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.32
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.31
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.30
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.29
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.28
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.27
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.26
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.25
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.24
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.23
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.22
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.21
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.20
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.19
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.18
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.17
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.16
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.14
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.13
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.12
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.11
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.10
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.9
patch
1 CVE
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev | ||
1.3.8
patch
2 CVEs
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev
CVE-2026-4270
GHSA-2cpp-j2fc-qhp7
PYSEC-2026-162
Mar 17, 2026
AWS API MCP File Access Restriction Bypass
Medium
Local
Low
None
DescriptionThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. This server acts as a bridge between AI assistants and AWS services, allowing you to create, update, and manage AWS resources across all available services. The server includes a configurable file access feature that controls how AWS CLI commands interact with the local file system. By default, file operations are restricted to a designated working directory (workdir), but this can be configured to allow unrestricted file system access (unrestricted) or to block all local file path arguments entirely (no-access). Description: Improper Protection of Alternate Path exists in the no-access and workdir feature of the AWS API MCP Server versions >= 0.2.14 and < 1.3.9 on all platforms may allow the bypass of intended file access restriction and expose arbitrary local file contents in the MCP client application context. To remediate this issue, users should upgrade to version 1.3.9. Affected versions
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
1.1.2
+ 19 more Show less
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
Fixed in
1.3.9
References
Updated Jun 08, 2026 · Source: OSV.dev | ||
1.3.7
patch
2 CVEs
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev
CVE-2026-4270
GHSA-2cpp-j2fc-qhp7
PYSEC-2026-162
Mar 17, 2026
AWS API MCP File Access Restriction Bypass
Medium
Local
Low
None
DescriptionThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. This server acts as a bridge between AI assistants and AWS services, allowing you to create, update, and manage AWS resources across all available services. The server includes a configurable file access feature that controls how AWS CLI commands interact with the local file system. By default, file operations are restricted to a designated working directory (workdir), but this can be configured to allow unrestricted file system access (unrestricted) or to block all local file path arguments entirely (no-access). Description: Improper Protection of Alternate Path exists in the no-access and workdir feature of the AWS API MCP Server versions >= 0.2.14 and < 1.3.9 on all platforms may allow the bypass of intended file access restriction and expose arbitrary local file contents in the MCP client application context. To remediate this issue, users should upgrade to version 1.3.9. Affected versions
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
1.1.2
+ 19 more Show less
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
Fixed in
1.3.9
References
Updated Jun 08, 2026 · Source: OSV.dev | ||
1.3.6
patch
2 CVEs
CVE-2026-16584
PYSEC-2026-3549
GHSA-29w2-fq35-v728
Aug 04, 2026
AWS API MCP Server Security Policy Bypass via Startup Initialization Failure
Critical
Local
Low
None
SummaryThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ImpactOn startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47 PatchesThis issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsAny one of the following prevents the bypass until you can upgrade:
ContactIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. AcknowledgementWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process. Affected versions
0.2.13
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
+ 57 more Show less
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.3
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.4
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
1.3.46
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
Fixed in
1.3.47
References
Updated Aug 04, 2026 · Source: OSV.dev
CVE-2026-4270
GHSA-2cpp-j2fc-qhp7
PYSEC-2026-162
Mar 17, 2026
AWS API MCP File Access Restriction Bypass
Medium
Local
Low
None
DescriptionThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. This server acts as a bridge between AI assistants and AWS services, allowing you to create, update, and manage AWS resources across all available services. The server includes a configurable file access feature that controls how AWS CLI commands interact with the local file system. By default, file operations are restricted to a designated working directory (workdir), but this can be configured to allow unrestricted file system access (unrestricted) or to block all local file path arguments entirely (no-access). Description: Improper Protection of Alternate Path exists in the no-access and workdir feature of the AWS API MCP Server versions >= 0.2.14 and < 1.3.9 on all platforms may allow the bypass of intended file access restriction and expose arbitrary local file contents in the MCP client application context. To remediate this issue, users should upgrade to version 1.3.9. Affected versions
0.2.14
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
1.0.0
1.0.1
1.0.2
1.1.0
1.1.1
1.1.2
+ 19 more Show less
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
Fixed in
1.3.9
References
Updated Jun 08, 2026 · Source: OSV.dev |