Medium 6.2Published Oct 2, 2026

CVE-2026-103957Server-side request forgery in the OAuth2 discovery handling in Loom for AWS

Updated under an hour ago (2026-10-19 08:30 UTC)

Does this affect you?

It affects AWS loom. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for AWS loom

Exploited in the last 30 days

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.

CVSS: 6.2 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N
Weakness (CWE): CWE-918, CWE-201
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: AMZN
NVD analysis: Awaiting Analysis
Record last updated: Oct 9, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

AWS loom aws:loom (from the name)	before 1.7.0	CNA record

References

https://github.com/awslabs/loom/releases/tag/v1.7.0release-notes, patch
https://aws.amazon.com/security/security-bulletins/2026-124-aws/vendor-advisory
https://github.com/awslabs/loom/security/advisories/GHSA-jcxf-gpf4-58hmthird-party-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.