Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
2.1

OpenClaw allows continued memory access after revocation

CVE-2026-100539 · published 23 days ago
Summary

The OpenClaw npm package lets a running process keep reading memory even after an administrator disables that permission. This means data that should be blocked can still be accessed until the process stops, potentially exposing sensitive information. Upgrade to version 2026.8.1 or later to ensure the disable command works correctly.

What to do
  • Update openclaw openclaw to version 2026.8.1 or later.
Affected software
VendorProductAffected versions
openclaw openclaw < 2026.8.1
Original advisory text
OpenClaw before 2026.8.1 Memory Access Control Bypass
OpenClaw (npm package 'openclaw') before 2026.8.1 fails to revoke memory tool access when an operator hot-disables memory configuration. Existing memory_search and memory_get tool instances retain the enabled configuration captured at creation time because the execution-time resolver treats explicit disablement like an unavailable configuration snapshot and restores the stale authority. As a result, during an already-running agent turn the model can continue searching and reading durable memory after the operator revoked that access, for the remainder of that run. Exploitation requires memory to be disabled while a previously created memory tool remains active. The issue is fixed in 2026.8.1.
References
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker partial control
Severity
2.1 Low
Exploitation
<1% chance of attack within 30 days
Type
CWE-863Incorrect Authorization
Timeline
Published26 Sep 2026
Updated19 Oct 2026
First seen26 Sep 2026
Sources
CVE-2026-100539 · NVD
CVE-2026-100539 · MITRE
CVE-2026-100539 · OSV
GHSA-chr6-w4m5-57fv · GHSA
Track software like this
Free during beta