CVE-2026-87912: AWS Security Agent plugin · Unverified ownership
Affects AWS Security Agent pluginSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 1.1.0 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.1.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade aws/agent-toolkit-for-aws to 1.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AWSAWS Security Agent plugin | Affected
| Fixed in– |
GitHubaws/agent-toolkit-for-awspkg:github/aws/agent-toolkit-for-awsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the AWS Security Agent plugin to version 1.1.0 or later, which includes the fix for this vulnerability. Additionally, verify that the scan output S3 bucket in your AWS account is owned by your account, as upgrading does not automatically release bucket names that may have been registered by third parties.
Description
CVE-2026-87912 is a vulnerability in the AWS Security Agent plugin before version 1.1.0 where missing verification of S3 bucket ownership could allow remote attackers to access private source archives of scanned workspaces. These archives may contain sensitive credentials and infrastructure state. The issue arises from the use of a pre-registered storage bucket named based on a publicly known account identifier. AWS has released version 1.1.0 to address this vulnerability. Users must also verify that their scan output buckets are owned by their own accounts, as upgrading does not reclaim bucket names already registered by third parties.