CVE-2026-103956: Unauthenticated Admin Takeover of AWS Labs Loom, Plus Two SSRF Issues
Loom is an AWS Labs open-source AI agent orchestration platform. In versions before 1.6.1, a deployment with no identity provider configured gave any network client full administrative control of the agent control plane through any request to the application API, including registering tool servers, reading stored integration credentials and rewriting IAM role policies attached to managed agent roles (CVE-2026-103956, CVSS 3.1 10.0). This was fixed in 1.6.1, released August 4, 2026.
Two further issues, fixed in 1.7.0, let an authenticated user with the mcp:write or a2a:write scope abuse outbound requests: CVE-2026-103957 could direct OAuth2 client secrets or another user's access token to a third-party endpoint, and CVE-2026-103958 could reach internal network locations, including the container's credential-vending endpoint, and read the responses.
After upgrading, AWS recommends rotating OAuth2 client secrets used for MCP/A2A integrations, revoking and re-issuing access tokens active during the affected window, and, if container role credentials were accessed, rotating them and reviewing CloudTrail. Credited to Kenneth Cox via coordinated disclosure.
- Loom < 1.6.1 (CVE-2026-103956)
- Loom < 1.7.0 (CVE-2026-103957, CVE-2026-103958)
- Loom 1.6.1 (CVE-2026-103956)
- Loom 1.7.0 (all three)