Skip to main content

Bedrock AgentCore Toolkit CVE-2026-106032

| EUVDEUVD-2026-94002 MEDIUM
Server-Side Request Forgery (SSRF) (CWE-918)
2026-10-06 AMZN
5.7
CVSS 4.0 · Vendor: AMZN
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as principal in shared AWS account
  2. Delivery
    Plant crafted OpenAPI external references in action group
  3. Exploit
    Victim imports Bedrock Agent via toolkit
  4. Execution
    Schema processor resolves malicious external $ref
  5. Impact
    Read local files and issue outbound SSRF requests

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to be an authenticated actor within the same AWS account as the victim (PR:L), and requires the victim to actively import a Bedrock Agent whose action group's associated OpenAPI content contains attacker-crafted external reference values that the toolkit's schema processor will resolve (UI:A / AT:P). It is limited to Amazon Bedrock AgentCore Starter Toolkit versions before 0.3.14; the supported replacement, the @aws/agentcore npm CLI, does not contain this issue. The principal limiting factors are therefore same-account authentication, the mandatory victim import action, and the narrow affected-version window - all of which prevent unauthenticated or non-interactive exploitation.

Impact

The vendor-supplied CVSS 4.0 vector (5.7, Medium) tells a consistent, low-urgency story: exploitation is network-reachable (AV:N) and technically simple (AC:L), but gated by three real constraints - the attacker must already be an authenticated principal in the SAME AWS account (PR:L), a specific attack condition must hold (AT:P, i.e. a crafted OpenAPI external reference in an action group), and a victim must actively perform an import action (UI:A). Impact is confined to confidentiality (VC:H via arbitrary local file read and SSRF-driven outbound requests), with no integrity or availability impact (VI:N/VA:N) and no scope change to subsequent systems (SC/SI/SA:N). Exploitation status: no public exploit identified at time of analysis - there is no KEV listing and no POC flag in the provided data, and no EPSS score was supplied, so widespread or opportunistic exploitation cannot be inferred. This is a genuine but bounded insider/same-account threat, not an internet-facing mass-exploitation risk; the combination of required same-account authentication plus victim interaction makes it a lower real-world priority than its CWE-918 (SSRF) class might suggest. Signals are mutually consistent - no contradiction between the vector and the description - though the absence of EPSS/KEV/POC means the exploitation-likelihood dimension is simply unmeasured rather than confirmed-low.

Exploit ScenarioDerived

A malicious or compromised principal already authenticated within the same AWS account crafts a Bedrock Agent action group whose associated OpenAPI content contains hostile external reference ($ref) values. When a legitimate user imports that Bedrock Agent using the AgentCore Starter Toolkit (before 0.3.14), the toolkit's schema processor resolves those references, causing the victim's environment to issue arbitrary outbound requests and disclose arbitrary local files. No public exploit code is identified at time of analysis; exploitation requires the victim to perform the import action.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

Server-side request forgery in the agent import functionality of Amazon Bedrock AgentCore Starter Toolkit versions before 0.3.14 allows an authenticated actor within the same AWS account to make the environment of a user importing a Bedrock Agent issue arbitrary outbound requests and read arbitrary local files. The attacker must supply crafted external reference values in the OpenAPI content associated with a Bedrock Agent action group, and exploitation requires the victim to actively import that agent; this narrow interaction requirement and the same-account authentication prerequisite limit the practical exposure, consistent with the vendor's Medium (CVSS 4.0 5.7) rating and our assessed CVSS 3.1 score of AV:N/AC:L/PR:L/UI:R with high confidentiality impact only. No public exploit code has been identified at time of analysis, and no known active exploitation has been reported.

RemediationAI

Upgrade to the vendor-released patch, bedrock-agentcore-starter-toolkit 0.3.14 (https://pypi.org/project/bedrock-agentcore-starter-toolkit/0.3.14/), and confirm no pinned or cached pre-0.3.14 copies remain in build pipelines or virtual environments. Because the package is deprecated, the recommended long-term path is to migrate to the supported @aws/agentcore npm CLI, which does not contain this vulnerability, and to retire toolkit-based import workflows once migration completes; the trade-off is a migration effort and any CLI behavior changes, but it removes the vulnerable code path entirely. Where immediate upgrade or migration is not possible, treat the import of untrusted Bedrock Agents as the risk boundary: only import agent definitions and action-group OpenAPI documents from trusted sources and pre-review OpenAPI content to reject external reference values (remote URLs, file-scheme or relative-path references) before import; this blocks the SSRF and local-file-read vectors but shifts a manual review burden onto operators and may reject legitimately reference-based schemas. Additional compensating controls include running imports in a least-privilege environment with restricted outbound network egress and no access to sensitive local files, which reduces the impact of a successful fetch but does not eliminate the underlying SSRF condition. Vendor guidance and any updates are published in the AWS security bulletin at https://staging.prod.website.marketing.aws.dev/security/security-bulletins/2026-127-aws/.

Affected VersionsENISA

bedrock-agentcore-starter-toolkit 0.1.4 ≤0.3.13

Affected Packages

euvd bedrock_agentcore_starter_toolkit no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic CWE-918 server-side request forgery arising in the OpenAPI schema-processing pipeline that the AgentCore Starter Toolkit uses when it imports a Bedrock Agent definition. When action-group OpenAPI content is parsed, external reference values (for example $ref entries pointing at remote or file-scheme locations) are resolved by the toolkit rather than being validated against an allow-list, so a crafted reference can coerce the importing environment into fetching arbitrary URLs and, by extension, reading arbitrary local files. The affected component is the Python package bedrock-agentcore-starter-toolkit (CPE cpe:2.3:a:aws:bedrock-agentcore-starter-toolkit:*:*:*:*:*:*:*:*), distributed via PyPI, and the vulnerable code path is the agent-import/schema-resolution logic in releases prior to 0.3.14. Because exploitation is gated behind an authenticated principal in the same AWS account plus a victim-initiated import of an agent whose OpenAPI content carries the malicious reference (CVSS 4.0 AT:P with UI:A; assessed CVSS 3.1 PR:L/UI:R), the attack is neither unauthenticated nor fully non-interactive, and the confidentiality-only impact (VC:H, VI:N, VA:N) reflects data exposure rather than code execution or service disruption.

Know when Bedrock Agentcore Starter Toolkit gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (AMZN) PRIMARY 5.7 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 5.7 MEDIUM

Authenticated same-account actor (PR:L) plants a crafted schema that a victim must import (UI:R); SSRF and local file read yield C:H with no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (AMZN).

CVSS VectorVendor: AMZN

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
Active
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Server-side request forgery in the OpenAPI schema processing of the agent import functionality in Amazon Bedrock AgentCore Starter Toolkit before 0.3.14 might allow an authenticated remote actor in the same AWS account to cause the environment of a user importing a Bedrock Agent to issue arbitrary outbound requests and read arbitrary local files, via crafted external reference values in the OpenAPI content associated with a Bedrock Agent action group.

To remediate this issue, users should upgrade to version 0.3.14. Note that bedrock-agentcore-starter-toolkit is deprecated. The @aws/agentcore npm CLI is the supported replacement and does not contain this issue. Migration to @aws/agentcore is the recommended long-term path.

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
Low
deprecated niche AWS developer toolkit, limited production footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy