CVE-2026-32919: OpenClaw · Write-scoped callers could reach admin-only session reset logic through `agent`
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 6.1 Medium : upgrade to 2026.3.11 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.3.11
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:HExploitation 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 17 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.3.11.
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
Upgrade openclaw-cli to version 2026.3.11 or later, where the vulnerability is fixed. The fix ensures that /new and /reset agent commands no longer route through the admin-only sessions.reset entry point. No other workarounds are documented.
Description
A vulnerability in openclaw-cli versions up to 2026.3.10 allows users with operator.write permissions to reset conversation sessions via the agent interface, bypassing the intended admin-only restriction on session resets. This occurs because the agent slash commands /new and /reset internally reuse admin-only reset logic without proper scope enforcement. The issue is fixed in version 2026.3.11.