// Security Advisory Triage

CVE-2026-87912 and CVE-2026-87913: Missing S3 bucket ownership verification in the AWS Security Agent plugin for aws-agents-for-devsecops and MCP Server

AWS security bulletins · published 2026-10-22 17:13 UTC
ACTION NEEDED VERIFY_EXPOSURE SECURITY
WHAT CHANGEDCVE-2026-87912 and CVE-2026-87913: Missing S3 bucket ownership verification in the AWS Security Agent plugin for aws-agents-for-devsecops and MCP Server. Source event: 2026-09-09T21:30:11+00:00. RSS discovery: 2026-10-21T22:46:20.970652+00:00.
WHY IT MATTERSCurrent bulletin, captured 2026-10-22T17:13:04.198Z: AWS Security Agent is a managed AWS service that provides AI-powered code security reviews, threat modeling, and penetration testing. We identified CVE-2026-87912, where a missing S3 bucket ownership verification in the AWS Security Agent plugin in Amazon aws-agents-for-devsecops before version 1.1.0 might allow remote attackers to obtain the private source archive of a scanned workspace, including credentials and infrastructure state contained in that archive, via a pre-registered storage bucket whose name is derived from a publicly known account identifier. We identified CVE-2026-87913, where a missing S3 bucket ownership verification in the AWS Security Agent MCP server before 0.2.0 might allow remote attackers to obtain the private source archive of a scanned workspace, including credentials and infrastructure state contained in that archive, via a pre-registered storage bucket whose name is derived from a publicly known account identifier. Impacted versions: <=1.0.0 >=0.1.0 AND <=0.1.5
WHAT TO DOCurrent vendor guidance, captured 2026-10-22T17:13:04.198Z (separate from RSS discovery 2026-10-21T22:46:20.970652+00:00): Resolution [B1]: This issues has been addressed in agent-toolkit-for-aws and awslabs.security-agent-mcp-server version 0.2.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. Workarounds [B2]: Upgrading does not release a bucket name that a third party has already registered. We recommend that you verify the scan-input bucket security-agent-scans-<account-id>-<region> in your account is owned by your own account. As a precaution, you can pre-create that bucket in your own account before first use so that the predictable name cannot be registered by another account. Source for [B1], [B2]: https://aws.amazon.com/security/security-bulletins/2026-105-aws/
Deterministic source evidence; confidence not scored Primary source ↗ written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
 https://aws.amazon.com/security/security-bulletins/rss/2026-105-aws/
 Wed, 09 Sep 2026 21:30:11 +0000
 
-Bulletin ID: 2026-105-AWS
-
-Scope: AWS
-
-Content Type: Important (requires attention)
-
-Publication Date: 09/10/2026 08:30 AM PDT
+Bulletin ID: 2026-105-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 09/10/2026 08:30 AM PDT
 Description:
 AWS Security Agent is a managed AWS service that provides AI-powered code security reviews, threat modeling, and penetration testing.
 We identified CVE-2026-87912, where a missing S3 bucket ownership verification in the AWS Security Agent plugin in Amazon aws-agents-for-devsecops before version 1.1.0 might allow remote attackers to obtain the private source archive of a scanned workspace, including credentials and infrastructure state contained in that archive, via a pre-registered storage bucket whose name is derived from a publicly known account identifier.
 We identified CVE-2026-87913, where a missing S3 bucket ownership verification in the AWS Security Agent MCP server before 0.2.0 might allow remote attackers to obtain the private source archive of a scanned workspace, including credentials and infrastructure state contained in that archive, via a pre-registered storage bucket whose name is derived from a publicly known account identifier.
-Impacted versions:
-
-- <=1.0.0
-
-- >=0.1.0 AND <=0.1.5
+Impacted versions: - <=1.0.0 - >=0.1.0 AND <=0.1.5
 Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.
SEPARATE BULLETIN CAPTURE · complete

Retrieved separately from the RSS discovery; this does not establish historical page content.

retrieval attempted2026-10-22T17:13:04.035Z
captured at2026-10-22T17:13:04.198Z
sourcehttps://aws.amazon.com/security/security-bulletins/2026-105-aws/
content SHA-256f00083cae7c8933ee1430950e6d456915fedcafd88ff7c9e03c77a01441d832e
CVE-2026-87912 and CVE-2026-87913: Missing S3 bucket ownership verification in the AWS Security Agent plugin for aws-agents-for-devsecops and MCP Server

Bulletin ID: 2026-105-AWS
Scope: AWS
Content Type: Important (requires attention)
Publication Date: 09/10/2026 08:30 AM PDT

Description:

AWS Security Agent is a managed AWS service that provides AI-powered code security reviews, threat modeling, and penetration testing.

We identified CVE-2026-87912, where a missing S3 bucket ownership verification in the AWS Security Agent plugin in Amazon aws-agents-for-devsecops before version 1.1.0 might allow remote attackers to obtain the private source archive of a scanned workspace, including credentials and infrastructure state contained in that archive, via a pre-registered storage bucket whose name is derived from a publicly known account identifier.

We identified CVE-2026-87913, where a missing S3 bucket ownership verification in the AWS Security Agent MCP server before 0.2.0 might allow remote attackers to obtain the private source archive of a scanned workspace, including credentials and infrastructure state contained in that archive, via a pre-registered storage bucket whose name is derived from a publicly known account identifier.

Impacted versions:

<=1.0.0

>=0.1.0 AND <=0.1.5

Resolution:

This issues has been addressed in agent-toolkit-for-aws and awslabs.security-agent-mcp-server version 0.2.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.

Workarounds:

Upgrading does not release a bucket name that a third party has already registered. We recommend that you verify the scan-input bucket security-agent-scans-<account-id>-<region> in your account is owned by your own account. As a precaution, you can pre-create that bucket in your own account before first use so that the predictable name cannot be registered by another account.

References:

CVE-2026-87912

CVE-2026-87913

GHSA-2px6-hhjp-3g5x

GHSA-3jxw-vj8m-8x77

Acknowledgement:

We would like to thank Nadav Claude Cohen from glow.io who reported this issue for collaborating with us through the coordinated vulnerability disclosure process.

Please email aws-security@amazon.com with any security questions or concerns.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningAWS Security Agent is a managed service and AI framework that developers integrate into CI/CD and DevSecOps pipelines. Credential and infrastructure state exposure is actionable.
signalsAWS managed service vulnerability · AI agent framework affected (aws-agents-for-devsecops) · MCP server affected · credential and infrastructure state exposure · remote attacker vector · affects developer tools and CI/CD integrations · two CVEs in security-critical service
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modeladvisory-evidence-v2 ($0.00000)