Loading vulnerability…
CVE-2026-53821 affects OpenClaw before version 2026.5.18. The vulnerability arises from improper authorization handling in WebSocket session establishment: the application accepts client-declared operator scopes before those scopes are bound to a server-approved pairing state or trusted-proxy authorization baseline. As a result, an unpaired Control UI client, or a restricted trusted-proxy Control UI client, can cause a live WebSocket connection to retain cached operator.admin authority and then use that elevated authorization to invoke admin-gated Gateway RPCs. The issue is an authorization weakness in session/scope handling rather than an authentication bypass in the abstract, and is mapped to CWE-862.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.