To remediate this issue, users should upgrade to version 1.7.0 or later.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sun, 04 Oct 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Aws
Aws loom |
|
| Vendors & Products |
Aws
Aws loom |
Fri, 02 Oct 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Fri, 02 Oct 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Server-side request forgery in the OAuth2 discovery handling in Loom for AWS | |
| Weaknesses | CWE-201 CWE-918 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: AMZN
Published:
Updated: 2026-10-06T18:03:10.415Z
Reserved: 2026-10-01T14:59:36.668Z
Link: CVE-2026-103957
No data.
Status : Awaiting Analysis
Published: 2026-10-02T19:16:39.893
Modified: 2026-10-06T19:17:40.007
Link: CVE-2026-103957
No data.
OpenCVE Enrichment
Updated: 2026-10-04T20:53:18Z