CVE-2026-87912
Received Received - Intake

AWS Security Agent Plugin S3 Bucket Ownership Verification Flaw

Publication date: 2026-09-10

Last updated on: 2026-09-10

Assigner: AMZN

Description
A missing S3 bucket ownership verification in the AWS Security Agent plugin in Amazon aws-agents-for-devsecops before 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. To remediate this issue, users should upgrade to version 1.1.0. Users should also verify that the scan output bucket in their account is owned by their own account, because upgrading does not release a bucket name that a third party has already registered.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-10
Last Modified
2026-09-10
Generated
2026-09-10
AI Q&A
2026-09-10
EPSS Evaluated
N/A
NVD
CVE-2026-87912
EUVD
EUVD-2026-75569

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
amazon aws-agents-for-devsecops to 1.1.0 (exc)
aws agent-toolkit-for-aws to 1.1.0 (exc)
awslabs security-agent-mcp-server to 0.2.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-341 A number or object is predictable based on observations that the attacker can make about the state of the system or network, such as time, process ID, etc.
CWE-283 The product does not properly verify that a critical resource is owned by the proper entity.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a missing S3 bucket ownership verification in the AWS Security Agent plugin for aws-agents-for-devsecops before version 1.1.0. Attackers could pre-register S3 bucket names derived from a target's AWS account ID and region. When users scanned workspaces, sensitive data like credentials and infrastructure state were uploaded to these attacker-owned buckets without validation.

Detection Guidance

To detect this vulnerability, check if your aws-agents-for-devsecops plugin is running version 1.0.0 or earlier. Verify S3 bucket ownership for the scan-input bucket (security-agent-scans-<account-id>-<region>) using AWS CLI commands like aws s3api head-bucket --bucket <bucket-name> --expected-bucket-owner <your-account-id>.

Impact Analysis

If exploited, attackers could access private source archives, credentials, and infrastructure state from scanned workspaces. This could lead to unauthorized access to systems, data breaches, or further attacks using exposed credentials. The impact depends on the sensitivity of the data processed by the tool.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's safeguards for protected health information. Organizations using affected versions may face compliance violations, legal penalties, and reputational damage due to potential data leaks.

Mitigation Strategies

Upgrade aws-agents-for-devsecops to version 1.1.0 or later. Verify ownership of your scan-input bucket and pre-create it in your AWS account to prevent third-party registration. Ensure all S3 operations include --expected-bucket-owner checks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-87912. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart