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.
CVE-2026-100539
Score 2.6 from GitHub Security Advisory (severity: LOW) published 2026-09-26. A secondary CVSS source baseline 2.6; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 2.6
- EG Score
- 2.6LOWhigh confidence
- EG Risk
- 16EG Risk 16/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity26% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.2%
- EPSS %ILE
- 9th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 26, 2026
Last Modified
September 28, 2026
References (2)
Vendor Advisories for CVE-2026-100539(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-01 22:37 UTCEG score recompute
- 2026-10-01 22:37 UTCGHSA enrichment
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-29 15:20 UTCEPSS rescore
- 2026-09-28 15:32 UTCEG score recompute
- 2026-09-28 15:32 UTCGHSA enrichment
- 2026-09-28 13:50 UTCEPSS rescore
- 2026-09-26 15:58 UTCEPSS rescore
- 2026-09-26 03:31 UTCEG score recompute
- 2026-09-26 03:31 UTCGHSA enrichment
- 2026-09-26 02:33 UTCEG score recompute
- 2026-09-26 02:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-100539?
When was CVE-2026-100539 disclosed?
Is CVE-2026-100539 actively exploited?
What is the CVSS score of CVE-2026-100539?
How do I remediate CVE-2026-100539?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-100539
Is Your Infrastructure Affected by CVE-2026-100539?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.