The disclosure
AWS disclosed three vulnerabilities in Loom for AWS. CVE-2026-103956 could allow a network client to obtain full administrative authority over the agent control plane in affected deployments without a configured identity provider, including registering tool servers, reading stored integration credentials and rewriting IAM role policies. CVE-2026-103957 involved OAuth credential disclosure, and CVE-2026-103958 involved outbound requests to internal network locations. AWS addressed the issues and recommends upgrading to Loom 1.7.0.
The authority problem
A compromised orchestration layer can change what an agent is technically capable of doing and can obtain credentials downstream systems accept as valid. That still does not establish legitimate enterprise authority for the resulting effect.
Identity, IAM permission and tool reachability are inputs to authority, not substitutes for it.
The authority-layer answer
Enterprise authority should remain independently rooted in valid mandates, delegations and exact-effect authorization. Unauthorized changes to an agent role, tool server or credential should not enlarge the authority envelope.
Technical privilege created by a compromised control plane is capability, not authority.
GitHub implication
If a compromised orchestrator obtains a GitHub token, registers a GitHub MCP server or expands GitHub App permissions, every consequential path should still converge on the same independent authority decision.
Sources
https://aws.amazon.com/security/security-bulletins/2026-124-aws/
NEXT STEP