Critical · CVSS 10.0CVE-2026-103956

Missing authentication for critical function in Loom for AWS

Answer in brief

CVE-2026-103956 records a Critical severity (CVSS 10.0) vulnerability in Missing authentication for critical function in Loom for AWS. The current sources do not mark it as known exploited. The current feed maps AWS/loom (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 2, 2026Updated Oct 2, 2026Source checked Oct 2, 2026First seen by HOL Oct 2, 2026Material review Oct 2, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 10.0
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 10.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps AWS/loom (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
AWS/loomgeneric	>=0 <1.6.1	1.6.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for AWS/loom.
Review the reported fix. Update AWS/loom to 1.6.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 2, 2026

Sources and claim methodology

Upstream source description

Missing authentication for critical function in the authentication dependency in Loom for AWS before 1.6.1 allowed remote actors to obtain super-admin authority over the agent control plane, including registering tool servers, reading stored integration credentials, and rewriting the IAM role policies attached to managed agent roles, via any request to the application API in a deployment where no identity provider is configured. To remediate this issue, users should upgrade to version 1.6.1 or later.

Quoted source text, attributed separately from HOL analysis.