Introduction
As of February 19, 2026, OpenClaw version 2026.2.17 has patched all known CVEs from the January security crisis. If you're running an older version, stop and upgrade. The vulnerabilities fixed in this release were severe: one-click remote code execution, Docker sandbox bypass, SSRF in the Gateway, unauthenticated webhooks, and path traversal in file uploads. The January CVEs made headlines; 2026.2.17 is the response.
This release isn't just patches. It also changes defaults: authentication is now required. The auth-none mode that many early adopters used for quick local testing has been deprecated. New installations can't use it. Existing configs will show a warning. The next major version will remove it entirely. The Foundation is drawing a line: OpenClaw must be secure by default.
The January security crisis — driven by the 135,000 exposed instances and the CVE disclosures — forced a fundamental rethink of OpenClaw's security posture. The Foundation could have patched the vulnerabilities and moved on. Instead, it used the crisis to implement security-by-default. Auth-none is gone. Encrypted credential storage is default. Docker sandbox is enforced. The message: OpenClaw will no longer ship in an insecure configuration. Users who want to run without auth must explicitly override defaults — and they'll get warnings. The ecosystem is maturing. Security is non-negotiable.
Patches
Every CVE from the January disclosure is addressed:
- CVE-2026-25253: Token isolation; no browser context leakage between sessions. Previously, tokens could bleed across users in certain configurations.
- CVE-2026-24763: Docker namespace isolation fixed. The sandbox for shell execution could be bypassed; now it can't.
- CVE-2026-26322: SSRF validation in the Gateway. Malicious URLs could trigger outbound requests to internal services.
- CVE-2026-26319: Webhook authentication (Telnyx, WhatsApp, etc.). Unauthenticated webhooks could be spoofed.
- CVE-2026-26329: Path traversal in file upload. Attackers could write files outside intended directories.
See the full CVE write-up for technical details. The short version: if you were exposed, you're not anymore — as long as you upgrade.
Each CVE had real-world impact. CVE-2026-25253 allowed session token leakage — an attacker could potentially access another user's browser context. CVE-2026-24763 allowed escape from the Docker sandbox — shell execution could affect the host. CVE-2026-26322 enabled SSRF — internal services could be probed or attacked. CVE-2026-26319 allowed webhook spoofing — attackers could inject messages into channels. CVE-2026-26329 allowed path traversal — arbitrary file writes. In combination with exposed instances, these were catastrophic. The patches close every vector. Upgrade eliminates the exposure.
Default Changes
Auth required by default. New installations cannot use auth-none. Existing auth-none configs will show a deprecation warning; the mode will be removed in the next major. Encrypted credential storage is now the default. Docker sandbox is enabled for shell execution — Skills that run shell commands are isolated. These changes may require config updates. If you've been running with auth-none for local testing, you'll need to add proper authentication before upgrading.
The default changes reflect a security-first philosophy. Previously, OpenClaw optimized for ease of setup. "Get running in 5 minutes" meant skipping auth for local use. The 135K exposed instances proved that "local" often meant "cloud VPS with public IP." The new defaults assume the worst: assume your deployment might be exposed, and secure it by default. Auth is required. Credentials are encrypted. Shell execution is sandboxed. If you need to relax these for a specific use case, you can — but you have to explicitly do it. The burden of proof has shifted from "opt-in to security" to "opt-out of security." Most users should never opt out.
Upgrade
For npm installs: npm update openclaw. For Docker: docker pull openclaw/openclaw:2026.2.17. Test in staging first. Review your config for auth changes. Run SecureClaw post-upgrade to verify your setup. If you're on 2026.2.16 or earlier, treat this as urgent. The CVEs were actively exploited in the wild.
Breaking Changes
Auth-none deprecation is the main one. If your config has auth: none, you'll see a warning. Plan to migrate to token-based or API-key auth before the next major. The Foundation has published migration guides. Most users can switch in under an hour. The alternative — staying on an unpatched version — isn't an option.
Wrapping Up
2026.2.17 is the secure baseline. Upgrade now. This release represents the Foundation's commitment to security by default. The January CVEs were a wake-up call. The deprecation of auth-none, the mandatory authentication, the sandbox improvements — they're the response. If you're on 2026.2.16 or earlier, treat the upgrade as urgent. The vulnerabilities were actively exploited. Don't wait. See OpenClaw security and CVEs for the full picture. Run SecureClaw after upgrading to verify your configuration.