CVE-2026-32897: Openclaw cli · OpenClaw reuses the gateway auth token in the owner ID prompt hashing fallback
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 2.1 Low : upgrade to 2026.7.1 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.7.1
CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and planned for release in OpenClaw CLI version 2026.2.22. This patch removes the fallback use of the gateway authentication tokens for owner ID prompt hashing and introduces a dedicated secret that is auto-generated and persisted when hash mode is enabled and no secret is set. Operators should upgrade to version 2026.2.22 once released to remediate this issue. Until then, setting a strong `commands.ownerDisplaySecret` can reduce risk.
Description
OpenClaw CLI versions up to 2026.2.21-2 reuse the gateway authentication token as a fallback secret for hashing the owner ID prompt when certain configuration settings are unset. This results in dual-use of a secret across authentication and prompt metadata hashing domains, potentially exposing hash outputs to third-party model providers. No direct plaintext token disclosure occurs. A fix is planned in version 2026.2.22 that removes this fallback and generates a dedicated secret for owner-display hashing.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-v6x2-2qvm-6gv8 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-32897 (opens in a new tab)
- github.com/openclaw/openclaw/commit/c99e7696e6893083b256f0a6c88fb060f3a76fb7 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- vulncheck.com/advisories/openclaw-authentication-token-reuse-in-owner-id-prompt-hashing-fallback (opens in a new tab)