Source-code disclosure via predictable S3 bucket reuse
Published Sep 10, 2026 · Updated Sep 10, 2026
Information disclosure in AWS Security Agent MCP Server 0.1.0 through 0.1.5 allows remote attackers to obtain scanned source archives. The bucket setup silently reuses a globally unique, deterministic S3 name after BucketAlreadyExists, and upload_to_s3 omits ExpectedBucketOwner. Exploitation requires pre-registering the victim-derived bucket name; a subsequent scan sends workspace code, credentials, and infrastructure state to that bucket.
Summary
What happened
Information disclosure in AWS Security Agent MCP Server 0.1.0 through 0.1.5 allows remote attackers to obtain scanned source archives. The bucket setup silently reuses a globally unique, deterministic S3 name after BucketAlreadyExists, and upload_to_s3 omits ExpectedBucketOwner. Exploitation requires pre-registering the victim-derived bucket name; a subsequent scan sends workspace code, credentials, and infrastructure state to that bucket.
The record
- CVE
- CVE-2026-87913
- Published
- Sep 10, 2026
- Updated
- Sep 10, 2026
- Vendor
- Amazon Web Services
- Product
- AWS Security Agent MCP Server
- Classifications
- T1567.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 10, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1.0 <=0.1.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Two-account S3 bucket-squatting proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo