Critical Authentication Bypass in OpenClaw 2026.5.14–2026.5.27
A new vulnerability, catalogued as PT-2026-60627 by Vulners, has been published detailing an authentication bypass affecting OpenClaw builds 2026.5.14‑beta.1 through 2026.5.27.
What Was Affected
The vulnerability is tied to exec approval flows — the mechanism OpenClaw uses to gate potentially destructive or high-privilege operations behind human authorization. In affected builds, the approval workflow could be bypassed under specific conditions, potentially allowing an attacker or compromised process to execute commands without the expected authorization check.
Affected Versions
- OpenClaw
2026.5.14‑beta.1through2026.5.27(inclusive)
Fixed in: 2026.6.x and later stable releases.
What Operators Should Do
- Check your current version — run
openclaw --versionor check the Gateway status page. - If you are on an affected range, upgrade to the latest stable release (
2026.7.1or later) before continuing normal operation. - Review exec approval logs for any unauthorized commands that may have executed during the affected window — look for approval bypass events in the Gateway audit trail.
- Ensure deployments are on a patched release as listed in the Vulners entry.
Context
This is the second security disclosure surfaced in as many days — following a GitLab advisory (GLAD) published July 16 that catalogued separate issues including path traversal in marketplace handling and Slack context filtering defects. The proximity of these two advisories suggests ongoing scrutiny of OpenClaw’s security surface as adoption scales.