Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-103956 – Authentication Bypass / Super-Admin Takeover – Loom for AWS before 1.6.1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-103956 is a critical missing-authentication vulnerability in Loom for AWS, an open-source AI agent orchestration platform maintained under AWS Labs. In deployments where no identity provider (IdP) is configured, the authentication dependency fails insecurely, allowing any unauthenticated network client to obtain super-admin authority over the entire agent control plane. The issue has been assigned a maximum CVSS v3.1 base score of 10.0 (Critical) and a CVSS v4.0 base score of 10.0 (Critical).

Technical details

  • Root cause: The application’s authentication dependency initializes with an insecure default (CWE-1188) — when no identity provider is configured for a deployment, the control-plane API enforces no authentication at all (CWE-306), rather than failing closed.
  • Trigger conditions: Any Loom for AWS deployment running a version prior to 1.6.1 that does not have an identity provider configured is exposed by default; no special configuration or prior access is required to trigger the flaw.
  • Attack vector: Network-based (AV:N) with low attack complexity, no privileges required, and no user interaction — exploitation is possible via any request to the application API.
  • Impact: A remote, unauthenticated actor can obtain full super-admin authority over the agent control plane, including:
    • Registering arbitrary tool servers into the orchestration environment
    • Reading stored integration credentials (e.g., OAuth2/OIDC secrets, API keys)
    • Rewriting IAM role policies attached to managed agent roles, enabling privilege escalation into connected AWS resources
  • The CVSS v3.1 vector indicates a Scope Change (S:C), reflecting that compromise of the vulnerable component can impact resources beyond its own security scope (e.g., downstream AWS IAM roles and credentials).

Affected software

  • Vendor: AWS (AWS Labs)
  • Product: Loom
  • Affected versions: All versions before 1.6.1 (version 0 up to, but not including, 1.6.1) deployed without an identity provider configured
  • Fixed version: 1.6.1 and later

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
  • CVSS v4.0 Base Score: 10.0 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Mitigation and recommended actions

  • Immediate: Upgrade Loom for AWS to version 1.6.1 or later, which requires explicit opt-in (via an environment variable) and loopback client validation for any local-development authentication bypass, and fails securely with HTTP 401 responses by default.
  • If immediate patching is not possible:
    • Ensure a proper identity provider (IdP) is configured for every Loom deployment — do not run deployments with no IdP configured, as this is the specific condition this vulnerability exploits.
    • Restrict network access to the Loom application API to trusted internal networks only (e.g., via security groups/firewalls) until the upgrade can be applied.
  • Post-upgrade hardening (recommended by the vendor for related issues disclosed alongside this CVE):
    • Rotate OAuth2/OIDC client secrets and any stored integration credentials.
    • Revoke and re-issue active access tokens.
    • Review AWS CloudTrail logs for unexpected IAM policy changes on managed agent roles, and rotate IAM role credentials if compromise is suspected.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge