CVE-2026-32970: OpenClaw: credential fallback bypasses local auth boundary
LOWOpenClaw before 2026.3.11 contains a fail-open credential logic flaw (CWE-636) where unresolvable local SecretRefs for gateway authentication silently fall back to remote credentials instead of failing closed, allowing a low-privileged local attacker to cause the CLI and helper paths to authenticate against unintended remote sources. Although the absolute CVSS score is low (2.5), the EPSS places this in the 99th percentile by exploitation likelihood, and OpenClaw's ecosystem has already demonstrated active credential-theft abuse — AIID incident #1368 documented malicious skills delivering the AMOS credential stealer through this same platform. No public exploit or Nuclei template exists, and the CVE is not in CISA KEV, so urgency is moderate rather than emergency. Organizations running OpenClaw in local mode should upgrade to 2026.3.11 immediately, audit all SecretRef configurations to confirm they resolve correctly, and rotate any remote gateway credentials that may have been exposed on affected deployments.
What is the risk?
Low absolute risk by CVSS (2.5) driven by local-only attack vector, high complexity, and confidentiality-only impact with no integrity or availability consequences. In an AI agent context the residual risk is meaningfully higher: credential boundary violations in agentic pipelines can silently escalate an agent's access to remote services, and the fail-open pattern (CWE-636) is particularly insidious because operators may never observe the fallback unless they specifically audit authentication logs. With only four downstream dependents the blast radius is contained, and the absence of public exploits or KEV listing reduces immediate operational pressure. The 99th-percentile EPSS ranking suggests this class of logic-level auth bypass attracts disproportionate attacker interest relative to its severity score.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| OpenClaw | pip | — | No patch |
Do you use OpenClaw? You're affected.
How severe is it?
What is the attack surface?
What should I do?
5 steps-
Patch immediately: upgrade OpenClaw to version 2026.3.11 or later.
-
Audit SecretRef configurations: verify that every gateway.auth.token and gateway.auth.password SecretRef referenced in local-mode deployments resolves successfully before deploying — treat any unresolvable reference as a blocking error.
-
Detect fallback events: until patched, instrument OpenClaw logs to alert on unexpected remote-credential authentication paths in local mode deployments.
-
Least-privilege enforcement: restrict local system access to OpenClaw service accounts to minimize the population that can trigger or exploit the fallback path.
-
Credential rotation: if any system ran an affected version with unresolvable local SecretRefs, rotate all associated remote gateway credentials as a precaution.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-32970?
OpenClaw before 2026.3.11 contains a fail-open credential logic flaw (CWE-636) where unresolvable local SecretRefs for gateway authentication silently fall back to remote credentials instead of failing closed, allowing a low-privileged local attacker to cause the CLI and helper paths to authenticate against unintended remote sources. Although the absolute CVSS score is low (2.5), the EPSS places this in the 99th percentile by exploitation likelihood, and OpenClaw's ecosystem has already demonstrated active credential-theft abuse — AIID incident #1368 documented malicious skills delivering the AMOS credential stealer through this same platform. No public exploit or Nuclei template exists, and the CVE is not in CISA KEV, so urgency is moderate rather than emergency. Organizations running OpenClaw in local mode should upgrade to 2026.3.11 immediately, audit all SecretRef configurations to confirm they resolve correctly, and rotate any remote gateway credentials that may have been exposed on affected deployments.
Is CVE-2026-32970 actively exploited?
No confirmed active exploitation of CVE-2026-32970 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-32970?
1. Patch immediately: upgrade OpenClaw to version 2026.3.11 or later. 2. Audit SecretRef configurations: verify that every gateway.auth.token and gateway.auth.password SecretRef referenced in local-mode deployments resolves successfully before deploying — treat any unresolvable reference as a blocking error. 3. Detect fallback events: until patched, instrument OpenClaw logs to alert on unexpected remote-credential authentication paths in local mode deployments. 4. Least-privilege enforcement: restrict local system access to OpenClaw service accounts to minimize the population that can trigger or exploit the fallback path. 5. Credential rotation: if any system ran an affected version with unresolvable local SecretRefs, rotate all associated remote gateway credentials as a precaution.
What systems are affected by CVE-2026-32970?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, local AI agent deployments, multi-tenant AI infrastructure.
What is the CVSS score for CVE-2026-32970?
CVE-2026-32970 has a CVSS v3.1 base score of 2.5 (LOW). The EPSS exploitation probability is 0.10%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0055 Unsecured Credentials AML.T0083 Credentials from AI Agent Configuration AML.T0084 Discover AI Agent Configuration AML.T0106 Exploitation for Credential Access Compliance Controls Affected
What are the technical details?
Original Advisory
OpenClaw before 2026.3.11 contains a credential fallback vulnerability where unavailable local gateway.auth.token and gateway.auth.password SecretRefs are treated as unset, allowing fallback to remote credentials in local mode. Attackers can exploit misconfigured local auth references to cause CLI and helper paths to select incorrect credential sources, potentially bypassing intended local authentication boundaries.
Exploitation Scenario
An attacker with low-privileged shell access on a host running OpenClaw in local mode identifies an existing misconfiguration where a SecretRef for gateway.auth.token points to a secret that no longer exists, or deliberately invalidates the referenced secret. When OpenClaw's CLI or a helper process next performs gateway authentication, the fallback logic treats the absent SecretRef as unset and switches silently to remote credentials. The attacker captures the remote credential material — via process inspection, log capture, or network interception of the outbound authentication request — and uses it to authenticate directly against the remote gateway service or downstream AI API, gaining access to resources that the local authentication boundary was specifically designed to prevent.
Weaknesses (CWE)
CWE-636 — Not Failing Securely ('Failing Open'): When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions.
- [Architecture and Design] Subdivide and allocate resources and components so that a failure in one part does not affect the entire product.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N References
Timeline
Related Vulnerabilities
CVE-2026-33579 9.9 OpenClaw: scope bypass escalates low-priv to admin
Same package: openclaw CVE-2026-32922 9.9 OpenClaw: privilege escalation to RCE via token scope bypass
Same package: openclaw CVE-2026-32038 9.8 OpenClaw: sandbox bypass enables container lateral movement
Same package: openclaw CVE-2026-53838 9.8 OpenClaw: approval scope bypass via reconnection state
Same package: openclaw CVE-2026-30741 9.8 OpenClaw: RCE via request-side prompt injection
Same package: openclaw