Is CVE-2026-53851 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53851 being exploited in the wild.

How severe is CVE-2026-53851?

Medium severity, with a CVSS score of 5.3, published 16 June 2026.

Which products and versions are affected?

openclaw (npm) SEMVER:introduced=0,fixed=2026.5.12; Openclaw < 2026.5.12, <= 2026.5.7.

Is there a fix for CVE-2026-53851?

Yes. openclaw (npm): upgrade to 2026.5.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53851 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-53851?

Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53851: OpenClaw Slack reaction event notification bypass

Q: Is there a fix for CVE-2026-53851?

Yes. openclaw (npm): upgrade to 2026.5.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-53851 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-53851?

Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53851 · Severity: medium · CVSS 5.3 · Published 2026-06-16

OpenClaw, an AI assistant platform, contains a flaw where Slack reaction events (such as adding an emoji to a message) are processed even if notifications for those events are disabled. This could allow unauthorized or unintended inputs to trigger automated agent actions, potentially leading to unexpected operations or resource consumption. Organizations using the Slack integration should update to the latest version to ensure their configuration settings are properly enforced.

Technologies: openclaw (npm), Openclaw. Vendors: npm, Openclaw.

Quick answers

Is CVE-2026-53851 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53851 being exploited in the wild.
How severe is CVE-2026-53851?: Medium severity, with a CVSS score of 5.3, published 16 June 2026.
Which products and versions are affected?: openclaw (npm) SEMVER:introduced=0,fixed=2026.5.12; Openclaw < 2026.5.12, <= 2026.5.7.
Is there a fix for CVE-2026-53851?: Yes. openclaw (npm): upgrade to 2026.5.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53851 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53851?: Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

openclaw (npm): upgrade to 2026.5.12 or later
```
npm install openclaw@2026.5.12
```

Technical details

An improper authorization vulnerability (CWE-285) exists in OpenClaw where Slack reaction events bypass configured notification settings. When a Slack reaction event is delivered to the configured application, it may enter the agent pipeline regardless of whether reaction notifications are disabled in the settings. This allows network-based attackers or users to trigger unintended agent processing by simply reacting to messages in Slack. The impact depends on the specific agent configuration and whether the pipeline processes lower-trust inputs. The issue is fixed in version 2026.5.12.

Affected products

openclaw openclaw <= 2026.5.7

Identifiers

CVE-2026-53851
GHSA-fcvx-5cxc-v5p8

Timeline

2026-05-28: disclosed: Advisory published to GitHub repository
2026-06-18: advisory: Published to GitHub Advisory Database
2026.5.12: patched: First stable patched version released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.