# CVE-2026-100537: OpenClaw before 2026.8.1 Authentication Bypass via Active Memory

> Denied senders can retrieve durable memory data via automatic recall, bypassing tool access restrictions in OpenClaw deployments using Active Memory.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-368p-92qh-j8q4, GHSA-wjfv-5qch-m5vj, MINI-mhxh-p98m-2fgh

## What is CVE-2026-100537?

CVE-2026-100537 is a low-severity missing authorization vulnerability in OpenClaw, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenClaw (npm package 'openclaw') before 2026.8.1 fails to apply the originating requester's effective tool policy during Active Memory automatic recall. In deployments that use Active Memory together with requester-specific tool rules, deterministic and hidden recall paths can retrieve durable memory and inject it into the agent's context even when toolsBySender explicitly denies that requester access to the memory tools (memory_search, memory_get). As a result, an admitted but denied sender can receive information derived from durable memory in the agent's response without directly invoking any memory tool. The issue is fixed in 2026.8.1.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-100537?


## How do I fix CVE-2026-100537?

Upgrade to a fixed version.

## Is CVE-2026-100537 being exploited?

There is no known exploitation of CVE-2026-100537 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100537 and fix it if it is affected.

What it is: CVE-2026-100537 is a low-severity missing authorization vulnerability in OpenClaw, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100537 in the wild and no public exploit code.

Affected product: OpenClaw. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100537/ (Markdown: https://insights.sbomify.com/CVE-2026-100537/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100537
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100537
- OSV: https://osv.dev/vulnerability/CVE-2026-100537

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100537/
Summaries are generated and may contain mistakes; the official description above is the record.