CVE-2026-87913: Missing S3 bucket ownership verification in the AWS Security Agent MCP server
AWS · AWS Security Agent MCP server
Fixed in 0.2.0 · Affected: AWS Security Agent MCP server before 0.2.0 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 38% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- AWS · AWS Security Agent MCP serverfrom 0.1.0 up to and including 0.1.5
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- AWS
- Published
- September 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-87913 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.