Quick answers
- Is CVE-2026-53860 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53860 being exploited in the wild.
- How severe is CVE-2026-53860?
- Medium severity, with a CVSS score of 4.2, published 16 June 2026.
- Which products and versions are affected?
- openclaw (npm) SEMVER:introduced=0,fixed=2026.5.7; Openclaw < 2026.5.7.
- Is there a fix for CVE-2026-53860?
- Yes. openclaw (npm): upgrade to 2026.5.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53860 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53860?
- 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.7 or later
npm install openclaw@2026.5.7
Technical details
An incorrect authorization vulnerability (CWE-863) exists in OpenClaw's BlueBubbles sender policy. The system matches allowlist entries against mutable conversation-level metadata rather than stable, immutable sender identities. A network-based attacker with low privileges who can influence conversation identifiers can bypass sender restrictions to receive agent responses. This issue is fixed in version 2026.5.7. Operators are advised to use stable identifiers and restrict BlueBubbles group access as a mitigation.
Affected products
- OpenClaw openclaw <= 2026.5.6
Identifiers
- CVE-2026-53860
- GHSA-8j37-5w68-wj2g
Timeline
- 2026-05-28: disclosed: Initial disclosure by reporter
- 2026-06-18: advisory: GitHub Advisory published
- 2026-05-28: patched: Version 2026.5.7 released