A critical vulnerability in OpenClaw (formerly Clawdbot/Moltbot), the popular open-source AI agent, allows attackers to achieve remote code execution with a single click. The flaw, tracked as CVE-2026-25253 (CVSS 8.8), was patched in version 2026.1.29 on January 30, 2026.

Vulnerability overview

AttributeValue
CVECVE-2026-25253
GHSAGHSA-r2c6-8jc8-g32w
CVSS8.8 (High)
TypeCross-Site WebSocket Hijacking (CSWSH)
Attack vectorMalicious link
User interactionSingle click
Fixed version2026.1.29
DiscovererMav Levin (depthfirst)

Technical analysis

The vulnerability chains multiple weaknesses into a one-click RCE exploit.

Vulnerability components

ComponentFileIssue
Settingsapp-settings.tsTrusted gatewayUrl query parameter without validation
Lifecycleapp-lifecycle.tsImmediately triggered connectGateway() with attacker URL
Gatewaygateway.tsIncluded auth token in handshake to malicious server

Root cause: Missing origin validation

Browser behaviorServer responsibility
Same-Origin Policy enforced for HTTPServer must validate WebSocket origins
Not enforced for WebSocket connectionsOpenClaw failed to validate origin header
Browser allows cross-origin WebSocketServer accepted connections from any website

“OpenClaw’s WebSocket server fails to validate the WebSocket origin header, accepting requests from any site.”

High-privilege token scopes

Stolen tokens carry dangerous permissions:

ScopeCapability
operator.adminFull administrative access
operator.approvalsDisable safety features

With these privileges, attackers don’t need sandbox escapes—they can simply disable safety features via the API.

The kill chain

Mav Levin at depthfirst demonstrated the attack executes in milliseconds:

PhaseActionTime
1Victim clicks malicious link0ms
2Browser connects to attacker’s WebSocket server~10ms
3OpenClaw sends authentication token automatically~20ms
4Attacker uses token to connect to victim’s OpenClaw~50ms
5Attacker sends exec.approvals.set with ask: "off"~100ms
6Attacker executes arbitrary commands on victim’s system~150ms

Total time from click to RCE: milliseconds.

Localhost bypass

Critically, localhost deployments are equally vulnerable. The victim’s browser becomes the bridge into their local network:

FactorImplication
Connection originates from legitimate browserBypasses localhost network restrictions
Browser has local network accessCSWSH bridges external attacker to local services
No firewall protectionAttack doesn’t traverse network boundary directly

“The vulnerability is exploitable even on instances configured to listen on loopback only, since the victim’s browser initiates the outbound connection.”

Exposure scale

Censys scanning data (January 31, 2026)

MetricValue
Publicly exposed instances21,000+
Alibaba Cloud hosting~30%
Default portTCP 18789
Authentication beyond gateway tokenOften absent

Who is affected

Deployment typeVulnerable?
Internet-exposed instancesYes
Localhost-only instancesYes (via CSWSH)
VPN-protected instancesYes (if user visits malicious site)
Any authenticated Control UI userYes

National advisory

The Belgium Centre for Cybersecurity (CCB) issued a national advisory:

“The vulnerability allows 1-click remote code execution when processing attacker-controlled content.”

Affected versions

VersionStatus
All versions up to v2026.1.24-1Vulnerable
v2026.1.29+Fixed

The fix

Version 2026.1.29 adds a gateway URL confirmation modal:

Before fixAfter fix
Automatic connection to any gatewayUrlUser must confirm unfamiliar gateway URLs
Silent token transmissionModal warns before connecting
No origin validationOrigin validation added

Remediation

Immediate actions

PriorityAction
CriticalUpgrade to v2026.1.29 or later
CriticalRotate gateway tokens (generate new authToken)
CriticalRotate API keys for all connected services
HighAudit authentication logs

Generating new gateway token

Rotate the authToken for your OpenClaw instance immediately—assume any token from before the patch is compromised if users accessed the Control UI.

Defense in depth

MeasurePurpose
Don’t expose OpenClaw to internetReduce attack surface
Use SSH tunnels or VPN for remote accessAuthenticated transport
Network-level ACLs on port 18789Limit connection sources
Monitor for unexpected originsDetect exploitation attempts

Detection

Indicators to monitor

IndicatorMeaning
WebSocket connections from unfamiliar originsPotential CSWSH
exec.approvals.set API callsSafety feature manipulation
ask: "off" parameterPrompt suppression
Unexpected command execution after browsingPost-exploitation
New or modified gateway tokensCredential theft

Log review

CheckLocation
WebSocket connection originsGateway logs
API calls to exec.approvalsControl plane logs
Command execution historySystem logs

AI agent security context

CVE-2026-25253 is separate from the ongoing malicious ClawHub skills campaign, but both highlight security challenges in the emerging AI agent ecosystem.

Why AI agents are high-risk targets

FactorRisk
System-level accessAgents execute commands on host
Autonomous operationReduced human oversight
Trust assumptionsUsers grant broad permissions
Rapid adoptionSecurity practices lag features

AI agent attack surface

ComponentRisk
Control UIThis vulnerability (CSWSH)
Skill marketplaceMalicious skills (separate issue)
LLM integrationsPrompt injection
Tool executionCommand injection

Recommendations

For OpenClaw users

PriorityAction
CriticalUpdate to v2026.1.29 immediately
CriticalRotate all credentials
HighAudit for signs of compromise
OngoingMonitor security advisories

For AI agent deployers

PriorityAction
HighInventory all AI agent deployments
HighReview network exposure
HighImplement authentication beyond default
OngoingTrack AI agent security research

For security teams

PriorityAction
HighAdd AI agents to vulnerability management
HighMonitor for CSWSH patterns
MediumDevelop AI agent security policies
OngoingThreat model AI agent deployments

Context

CVE-2026-25253 demonstrates that AI agent security requires the same rigor as traditional application security—and potentially more, given the system-level access these tools often require.

The trivial exploitation requirements (single click), the bypass of localhost restrictions, and the availability of 21,000+ exposed instances make this an emergency patch situation. As autonomous AI assistants gain system-level access, vulnerabilities enabling unauthorized control become critical-severity issues regardless of CVSS scores.

Users running OpenClaw should treat this as an emergency patch, particularly given that the attack works even against “secure” localhost-only deployments.