CVE-2026-103957
Description
A flaw was found in Loom. An authenticated remote attacker can exploit this vulnerability by supplying a crafted discovery document address during the registration of a tool server or remote agent configured for delegated authentication. This triggers a Server-Side Request Forgery (SSRF), causing the application to send requests to arbitrary internal network locations and allowing the attacker to obtain access tokens of other users, leading to unauthorized information disclosure.
Statement
A MODERATE information disclosure vulnerability was found in the OAuth2 discovery handling of Loom for AWS, an upstream AWS Labs open-source AI agent orchestration platform. An authenticated remote user holding the mcp:write or a2a:write scope can supply a crafted discovery document address when registering a tool server or remote agent configured for delegated authentication. The resulting server-side request forgery (SSRF) causes the application to issue requests to arbitrary internal network locations and can direct OAuth2 client secrets or the access token of another user of the deployment to a third-party-controlled endpoint, leading to unauthorized information disclosure. The current affected scope of this flaw contains no Red Hat products, as Loom is an upstream AWS project and no Red Hat offering ships it. Red Hat rates this flaw MODERATE (CVSS 3.1 score 4.5) rather than the upstream rating of IMPORTANT (CVSS 4.0 score 8.2), primarily because Red Hat scores the scope as unchanged, consistent with Red Hat CVSS guidance for SSRF flaws where requests remain within the application's own security authority, whereas the upstream assessment scores the scope as changed.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Upstream has fully addressed this issue in Loom for AWS 1.7.0; users of the upstream project should upgrade to the latest version and ensure any forked or derivative code is patched to incorporate the fix.
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data
Integrity
Technical Impact: Execute Unauthorized Code or Commands
Access Control
Technical Impact: Bypass Protection Mechanism
By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.