CVE-2026-53847: OpenClaw < 2026.5.6 - Privilege Escalation via Active Memory Write Scope

Published Jun 16, 2026
·
Updated

Summary

Active Memory write scope could mutate global config. In affected versions, a Gateway caller with operator.write access to the affected command could change global configuration without requiring operator.admin.

This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed.

Impact

When the affected feature is enabled and reachable, this could apply configuration changes beyond the intended write scope. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path.

Patched Versions

The first stable patched version is 2026.5.6.

Mitigations

limit Active Memory write access to trusted operators until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.

Other sources

OpenClaw before 2026.5.6 contains a privilege escalation vulnerability in the Active Memory write scope that allows Gateway operators with operator.write access to modify global configuration without requiring operator.admin privileges. Attackers with operator.write access can exploit insufficient scope validation to apply unauthorized configuration changes beyond the intended write scope.

MITRE

Affected Software

4 affected componentsFixes available
OpenClaw OpenClaw<2026.5.6
OpenClaw Openclaw Node.js<2026.5.6
OpenClaw Openclaw Node.js=2026.5.6-beta1
npm/openclaw<=2026.5.5
2026.5.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/openclaw to a version that resolves this vulnerability.

    Fixed in 2026.5.6
  2. Configuration

    Disable Active Memory write access when it is not required.

    OpenClaw Active Memory write access = disabled
  3. Configuration

    Limit Active Memory write access to trusted operators until patched.

    OpenClaw Active Memory write access = restricted to trusted operators
  4. Configuration

    Keep channel allowlist narrow.

    OpenClaw channel allowlist = narrow
  5. Configuration

    Keep tool allowlist narrow.

    OpenClaw tool allowlist = narrow
  6. Compensating control

    Avoid sharing one Gateway between mutually untrusted users.

Event History

Jun 16, 2026
CVE Published
via MITRE·06:04 PM
Data Sourced
via MITRE·06:04 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeaknessAffected Software
Jun 18, 2026
Advisory Published
via GitHub·08:15 PM
Data Sourced
via GitHub·08:15 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-53847?

CVE-2026-53847 has a medium severity rating of 5.3.

2

What vulnerability does CVE-2026-53847 describe?

CVE-2026-53847 describes a privilege escalation vulnerability in OpenClaw that allows Gateway callers with `operator.write` access to mutate global configuration.

3

Who is affected by CVE-2026-53847?

Users of OpenClaw versions prior to 2026.5.6 that have `operator.write` permissions are affected by CVE-2026-53847.

4

How do I fix CVE-2026-53847?

To fix CVE-2026-53847, update OpenClaw to version 2026.5.6 or later.

5

What potential impact does CVE-2026-53847 have?

CVE-2026-53847 can allow unauthorized changes to global configuration, potentially leading to further exploitation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203