Is CVE-2026-103958 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-103958 being exploited in the wild.

How severe is CVE-2026-103958?

Critical severity, with a CVSS score of 10, published 2 October 2026.

Which products and versions are affected?

AWS Loom for AWS before 1.6.1 (CVE-2026-103956); before 1.7.0 (CVE-2026-103957, CVE-2026-103958).

Is there a fix for CVE-2026-103958?

Yes: fixed in 1.6.1 (CVE-2026-103956); 1.7.0 (CVE-2026-103957, CVE-2026-103958). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-103958 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-103958?

Check whether you run Amazon AWS or AWS Loom for AWS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-103958: Loom for AWS authentication bypass and credential disclosure

CVE-2026-103958 · Severity: critical · CVSS 10 · Published 2026-10-02

Loom for AWS is an open-source AI agent orchestration platform that manages automated workflows and integrations on AWS. Three critical issues allow attackers to bypass authentication to gain full administrative control, steal OAuth2 tokens and credentials, and intercept outbound requests containing sensitive data. Organizations using Loom for AWS should upgrade immediately to version 1.7.0 to prevent unauthorized access to agent controls and credential theft.

Technologies: Amazon AWS. Vendors: Amazon, AWS.

Quick answers

Is CVE-2026-103958 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-103958 being exploited in the wild.
How severe is CVE-2026-103958?: Critical severity, with a CVSS score of 10, published 2 October 2026.
Which products and versions are affected?: AWS Loom for AWS before 1.6.1 (CVE-2026-103956); before 1.7.0 (CVE-2026-103957, CVE-2026-103958).
Is there a fix for CVE-2026-103958?: Yes: fixed in 1.6.1 (CVE-2026-103956); 1.7.0 (CVE-2026-103957, CVE-2026-103958). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-103958 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-103958?: Check whether you run Amazon AWS or AWS Loom for AWS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 1.6.1 (CVE-2026-103956); 1.7.0 (CVE-2026-103957, CVE-2026-103958)

Technical details

CVE-2026-103956 is an authentication bypass in the auth dependency (CWE-306, CWE-1188) affecting versions before 1.6.1, where any network client can obtain admin authority if no identity provider is configured. CVE-2026-103957 (CWE-918, CWE-201) allows authenticated users with mcp:write or a2a:write scope to configure OAuth2 discovery URLs that exfiltrate client secrets or access tokens to attacker-controlled endpoints; version 1.6.1 partially mitigated this but 1.7.0 fully addresses it. CVE-2026-103958 (CWE-918) involves similar outbound request handling issues in tool server and remote agent connections.

Affected products

AWS Loom for AWS before 1.6.1 (CVE-2026-103956); before 1.7.0 (CVE-2026-103957, CVE-2026-103958)

Identifiers

CVE-2026-103958
CVE-2026-103957
CVE-2026-103956

Timeline

2026-10-02: disclosed
2026-08-04: patched: 1.6.1 released with fix for CVE-2026-103956; partial mitigation for CVE-2026-103957
2026-10-02: patched: 1.7.0 released with full fixes for CVE-2026-103957 and CVE-2026-103958

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.