CVE-2026-103957

waiting for further signalsZero needs more public information before it can validate it.

GHSA-jcxf-gpf4-58hm ↗EUVD-2026-91772 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
AWS loom <1.7.0
fixed in 1.7.0
CWE-918 Server-Side Request Forgery (SSRF)
ETK-2026-394, permanent identifier
18d 17h 20msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+6h28m
0
+2h
+4h
+8h
+10h
+12h

description

AWS loom versions before 1.7.0 mishandle OAuth2 discovery addresses used for delegated-authentication tool servers or remote agents. An authenticated user with registration access may induce requests to internal network locations and potentially obtain another deployment user's access token.

mitigation

Upgrade loom to version 1.7.0 or later. Restrict tool-server and remote-agent registration to trusted administrators until the update is applied.

fixed in 1.7.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.38%30th percentile
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 19:06Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-02 19:06Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-103957

{
  "etk_id": "ETK-2026-394",
  "cve_id": "CVE-2026-103957",
  "display_id": "CVE-2026-103957",
  "ghsa_id": "GHSA-jcxf-gpf4-58hm",
  "euvd_id": "EUVD-2026-91772",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Server-side request forgery in AWS loom OAuth2 discovery",
  "summary": "AWS loom versions before 1.7.0 mishandle OAuth2 discovery addresses used for delegated-authentication tool servers or remote agents. An authenticated user with registration access may induce requests to internal network locations and potentially obtain another deployment user's access token.",
  "mitigation": "Upgrade loom to version 1.7.0 or later. Restrict tool-server and remote-agent registration to trusted administrators until the update is applied.",
  "vendor": "AWS",
  "product": "loom",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<1.7.0"
      ],
      "ecosystem": "loom for aws",
      "fixed_versions": [
        "1.7.0"
      ],
      "package_name": null,
      "purl": null
    }
  ],
  "cwes": [
    918
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": 0.0038,
  "epss_percentile": 0.3041,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.747926616666668,
  "t0_at": "2026-10-02T19:06:52.707000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T19:06:52.707000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T19:06:52.707000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103957"
    }
  }
}

published 2026-10-03 01:16Z
last change 2026-10-21 17:47Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.