OpenClaw CVE History
& Security Incidents
A transparent record of every significant security incident in the OpenClaw ecosystem — what happened, who was affected, and what action you need to take.
Known Vulnerabilities & Incidents
CVE-2026-25253 — Zero-Click Remote Code Execution via WebSocket
docker inspect openclaw | grep -i image. If not, update immediately: cd ~/openclaw && docker compose pull && docker compose up -d. Also verify port 3000 is NOT exposed to the internet in your firewall.ClawHavoc Campaign — 341 Malicious ClawHub Skills
Both incidents illustrate the key security advantage of managed OpenClaw hosts like xCloud: CVE-2026-25253 was patched fleet-wide within hours of disclosure, requiring zero action from users. Self-hosted instances that weren’t actively monitored remained vulnerable. If you self-host, automated weekly updates are essential — see our updates guide.
How to Get Security Alerts
Don’t wait to read about CVEs on Reddit. Set up alerts so you hear about them within hours of disclosure.
Go to github.com/open-claw/openclaw → Watch → Custom → check “Security advisories”. GitHub emails you immediately when a new security advisory is published for the repository. This is the fastest notification path.
Also subscribe to the OpenClaw Discord #security channel — critical vulnerabilities are announced there simultaneously with GitHub. For enterprise users, consider integrating OpenClaw’s repository with a security scanning tool like Dependabot or Snyk for automated dependency vulnerability detection.
Stay Informed, Stay Protected
Set up automated updates and GitHub security alerts — the two steps that keep you safe with minimal ongoing effort.
Automated Updates GuideSecurity Hardening →
