cve.bz

CVE-2026-103957 aws loom: SSRF

8.2 highEPSS 0.4%

High (8.2) in aws loom. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Server-side request forgery in the OAuth2 discovery handling in Loom for AWS before 1.7.0 might allow an authenticated remote user to obtain the access token of another user of the deployment and to cause the application to issue requests to arbitrary internal network locations, via a crafted discovery document address supplied when registering a tool server or remote agent configured for delegated authentication. To remediate this issue, users should upgrade to version 1.7.0 or later.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

CVSS 3.1

6.2 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-16. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-201 Insertion of Sensitive Information Into Sent Data
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-103957 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103957?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103957?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-103957 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
AWS loombefore 1.7.0

Red Hat

Red Hat rates this Moderate.

Red Hat's 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.

Red Hat's 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.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-103957.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High
  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-217 Exploiting Incorrectly Configured SSL/TLS Likelihood: Low
  • CAPEC-612 WiFi MAC Address Tracking Severity: Low
  • CAPEC-613 WiFi SSID Tracking Severity: Low
  • CAPEC-618 Cellular Broadcast Message Request Severity: Low
  • CAPEC-619 Signal Strength Tracking Severity: Low
  • CAPEC-621 Analysis of Packet Timing and Sizes Severity: Low
  • CAPEC-622 Electromagnetic Side-Channel Attack Severity: Low
  • CAPEC-623 Compromising Emanations Attack Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON