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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
Present
Additional conditions required
Privileges Required
None
No privileges needed
User Interaction
Passive
Minimal interaction
Impact Assessment
Confidentiality
None
No data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v4.0
References 3
https://aws.amazon.com/security/security-bulletins/2026-105-aws/
ff89ba41-3aa1-4d27-914a-91399e9639e5
https://github.com/aws/agent-toolkit-for-aws/commit/1c0dfd4f677237ee97697692099…
ff89ba41-3aa1-4d27-914a-91399e9639e5
https://github.com/aws/agent-toolkit-for-aws/security/advisories/GHSA-2px6-hhjp…
ff89ba41-3aa1-4d27-914a-91399e9639e5