CVE-2026-87913: CWE-283 Unverified ownership in AWS AWS Security Agent MCP server
A missing S3 bucket ownership verification in the AWS Security Agent MCP server before 0.2.0 version 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 0.2.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.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-87913) in AWS Security Agent MCP server prior to version 0.2.0 is due to missing verification of S3 bucket ownership. An attacker can exploit this by using a pre-registered storage bucket whose name is derived from a publicly known AWS account identifier, potentially gaining access to private source archives of scanned workspaces. These archives may contain sensitive information such as credentials and infrastructure state. The vulnerability has a CVSS 3.1 score of 5.9, reflecting medium severity with network attack vector, high complexity, no privileges required, and user interaction needed. AWS has issued an official fix in version 0.2.0 and advises users to verify bucket ownership to prevent unauthorized access.
Potential Impact
If exploited, remote attackers could obtain private source archives from scanned workspaces, including sensitive credentials and infrastructure state data. This could lead to unauthorized disclosure of confidential information. The vulnerability does not allow integrity or availability impacts but compromises confidentiality.
Mitigation Recommendations
An official fix is available in AWS Security Agent MCP server version 0.2.0. Users should upgrade to this version promptly. Additionally, users must verify that the scan output S3 bucket is owned by their own AWS account, as upgrading does not reclaim bucket names that third parties may have already registered. Follow the vendor advisory at https://aws.amazon.com/security/security-bulletins/2026-105-aws/ for detailed remediation guidance.
CVE-2026-87913: CWE-283 Unverified ownership in AWS AWS Security Agent MCP server
Description
A missing S3 bucket ownership verification in the AWS Security Agent MCP server before 0.2.0 version 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 0.2.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 v3.1
Score 5.9medium
Affected software
pkg:pypi/awslabs-security-agent-mcp-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-87913) in AWS Security Agent MCP server prior to version 0.2.0 is due to missing verification of S3 bucket ownership. An attacker can exploit this by using a pre-registered storage bucket whose name is derived from a publicly known AWS account identifier, potentially gaining access to private source archives of scanned workspaces. These archives may contain sensitive information such as credentials and infrastructure state. The vulnerability has a CVSS 3.1 score of 5.9, reflecting medium severity with network attack vector, high complexity, no privileges required, and user interaction needed. AWS has issued an official fix in version 0.2.0 and advises users to verify bucket ownership to prevent unauthorized access.
Potential Impact
If exploited, remote attackers could obtain private source archives from scanned workspaces, including sensitive credentials and infrastructure state data. This could lead to unauthorized disclosure of confidential information. The vulnerability does not allow integrity or availability impacts but compromises confidentiality.
Mitigation Recommendations
An official fix is available in AWS Security Agent MCP server version 0.2.0. Users should upgrade to this version promptly. Additionally, users must verify that the scan output S3 bucket is owned by their own AWS account, as upgrading does not reclaim bucket names that third parties may have already registered. Follow the vendor advisory at https://aws.amazon.com/security/security-bulletins/2026-105-aws/ for detailed remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- AMZN
- Date Reserved
- 2026-09-09T15:23:10.427Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Is Cloud Service
- true
- Vendor Advisory Urls
- [{"url":"https://aws.amazon.com/security/security-bulletins/2026-105-aws/","vendor":"AWS"}]
Threat ID: 6aa2d18d8744ddd5a6dabc0c
Added to database: 09/10/2026, 15:49:33 UTC
Last enriched: 09/10/2026, 16:37:09 UTC
Last updated: 09/10/2026, 17:00:15 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.