Skip to content
AgentProv

2026-10-08 · 2026-Q4

"AgentCorruption": One Prompt to an Amazon Bedrock AgentCore Agent Yields Credentials for Every Agent in the Account and Region

Primary layerL1 CredentialSecondary:L6 Identity / Run

Should this run hold this key at all?

The question layer 1 asks, and failed here.
Fixable
Vendor patch
Vendor response
Disputed
In the wild
No
Actor
Attacker

Target

Amazon Bedrock AgentCore runtime (Firecracker MicroVM) and its default execution role

Impact

Zenity Labs showed that chat access to a single exposed AgentCore agent was enough to trigger SSRF against the Instance Metadata Service (IMDSv1 until February 14, 2026) and obtain the agent's IAM role credentials. Because the default role covered all AgentCore resources in the region, those credentials could invoke other agents, read their conversations, plant persistent memories, pull secrets from Secrets Manager, and fetch container images. Zenity disclosed in December 2025; AWS closed the report as "informative" on April 12, 2026, the excessive permissions were still present on June 22, and Zenity found them addressed by September 29. AWS said the research "misrepresents documented behavior as a vulnerability." The attack did not cross account boundaries

Root cause

Insufficient network isolation between the agent sandbox and instance metadata, plus a default execution role scoped to every agent in the region rather than one

Sources

Catalog

Cite this: AgentProv incident record: "AgentCorruption": One Prompt to an Amazon Bedrock AgentCore Agent Yields Credentials for Every Agent in the Account and Region (2026-10-08). https://agentprov.com/incidents/2026-10-08-agentcorruption-one-prompt-to-an-amazon-bedrock-agentcore-agent-yields