CVE-2026-4269: AWS Bedrock AgentCore Starter Toolkit · Generation of Predictable Numbers or Identifiers
Affects AWS Bedrock AgentCore Starter ToolkitSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 0.1.13 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.1.13
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Upgrade Bedrock AgentCore Starter Toolkit and aws/bedrock-agentcore-starter-toolkit to 0.1.13.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AWSBedrock AgentCore Starter Toolkit | Affected
| Fixed in
|
GitHubaws/bedrock-agentcore-starter-toolkitpkg:github/aws/bedrock-agentcore-starter-toolkitOther 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
A patch is available in AWS Bedrock AgentCore Starter Toolkit version v0.1.13. Users should upgrade to this version to remediate the vulnerability. Users who built the toolkit before September 24, 2025, or are already on version v0.1.13 or later are not affected.
Description
A vulnerability in AWS Bedrock AgentCore Starter Toolkit before version v0.1.13 allows remote code execution due to missing S3 ownership verification during the build process. This affects users who built the toolkit after September 24, 2025, on versions prior to v0.1.13. Upgrading to version v0.1.13 mitigates the issue.