CVE-2026-53808: OpenClaw Approval Policy Bypass in Skill Workshop Apply Flow
OpenClaw versions prior to 2026.5.6 contain a bypass in their Skill Workshop approval controls. An attacker can force workshop changes to be applied immediately—bypassing the system's built-in approval requirement—by directly calling an agent tool with apply: true. This means configuration modifications intended to require manager review can slip through without authorization. The vulnerability requires user interaction (clicking a link or opening a message) but no special privileges to trigger.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
- Weaknesses (CWE)
- CWE-863
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-11 / 2026-06-17
NVD description (verbatim)
OpenClaw before 2026.5.6 contains an approval policy bypass vulnerability in the Skill Workshop apply flow that allows agent tool calls to set apply: true despite approvalPolicy: pending configuration. Attackers can exploit this by reaching the affected apply path to apply workshop changes before the expected approval step, potentially modifying configurations without proper authorization.
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-53808 is an authorization bypass in OpenClaw's Skill Workshop apply flow. The vulnerability exists because the system fails to properly enforce the approvalPolicy: pending configuration when agent tool calls set apply: true on the apply endpoint. An unauthenticated attacker can reach the affected apply path and cause workshop changes to be committed before the expected approval gate. The root cause relates to insufficient authorization checks (CWE-863: Incorrect Authorization) in the apply flow logic, allowing attackers to circumvent approval workflows that are otherwise configured in the system.
Business impact
This vulnerability enables unauthorized modification of OpenClaw workshop configurations in environments where approval workflows are in place. The security control designed to enforce review and authorization before deploying changes can be bypassed, creating a window for unauthorized or malicious configuration changes. For regulated organizations relying on OpenClaw for agent tool management, this could violate compliance requirements around change management. For all users, it undermines trust in the approval workflow and could allow misuse of workshop features if an attacker gains access to the apply endpoint.
Affected systems
OpenClaw versions before 2026.5.6 are vulnerable. This includes all prior release branches. Organizations running OpenClaw in production should check their version immediately. The vulnerability is specific to the Skill Workshop apply flow within the OpenClaw platform.
Exploitability
Exploitability is moderate. The attack requires network access to reach the apply endpoint and requires user interaction (such as following a crafted link or being directed to a malicious request). No authentication is required to exploit the vulnerability, and no special technical privileges are needed. An attacker could craft a request targeting the workshop apply flow and trick a user into triggering it, or directly reach the endpoint if it is exposed. The CVSS vector AV:N/AC:L/UI:R reflects this profile: network-accessible, low attack complexity, and user interaction required.
Remediation
Upgrade OpenClaw to version 2026.5.6 or later, which includes proper authorization checks for the apply endpoint and enforces the approvalPolicy: pending configuration. Organizations should verify the fix is applied by checking version numbers and reviewing the Skill Workshop apply flow behavior after patching. Until patching is complete, monitor access to the workshop apply endpoint and restrict which users can trigger workflow changes.
Patch guidance
Download and deploy OpenClaw 2026.5.6 or any later release available from the vendor. Apply the patch to all instances running the Skill Workshop feature. The patch addresses the authorization check failure by validating approvalPolicy: pending before allowing apply: true to take effect. Test the patch in a non-production environment first to confirm approval workflows are re-enforced as expected. Verify that any pending approvals are no longer bypassed after the update.
Detection guidance
Monitor OpenClaw logs for direct calls to the apply endpoint in the Skill Workshop flow, particularly those originating from unexpected sources or made without corresponding approval records. Look for apply: true requests that lack a matching approval_workflow_completed entry. Alert on any workshop configuration changes that bypass the approval log. If your environment logs agent tool calls, flag any tool invocations that directly set apply: true without prior authorization. Review access patterns to the apply path and cross-reference them against your approval audit trail.
Why prioritize this
Although this is rated MEDIUM severity (CVSS 6.5), it directly undermines a critical control—approval workflows. In environments where approval policies are business-critical for compliance or security, this vulnerability represents a significant control failure that should be patched promptly. Organizations heavily reliant on OpenClaw for agent tool governance should treat this as high-priority. For others, it remains important but not critical.
Risk score, explained
The CVSS 6.5 MEDIUM score reflects the vulnerability's network accessibility, low attack complexity, and requirement for user interaction. The impact is integrity-focused (I:H)—unauthorized configuration changes—with no impact on confidentiality or availability. The score appropriately captures the moderate threat: the vulnerability is easily reachable but requires user interaction and is limited to unauthorized modifications rather than data exposure or service disruption. Organizations with strict change management requirements may rate this higher in their own risk assessments.
Frequently asked questions
Can an attacker exploit this without the approvalPolicy: pending configuration?
The vulnerability specifically bypasses approvalPolicy: pending. If your workshop does not use approval policies, you are not at risk from this particular bypass. However, it is a sign of weak authorization logic in the apply flow that could be exploited in other ways—update anyway.
Do I need approval from OpenClaw to apply the patch?
No. The patch is a standard security update that you should apply following your normal change management process. OpenClaw has published version 2026.5.6 as the remediation. Test it and deploy at your earliest opportunity.
Will this patch disrupt existing workshops or pending approvals?
The patch restores proper enforcement of approval workflows. Any changes that were pending approval will remain pending. The patch should not disrupt legitimate workflows, only prevent the bypass. Test in staging before deploying to production to verify compatibility with your setup.
Is there a workaround if I cannot patch immediately?
Limit network access to the workshop apply endpoint to trusted internal users only. Disable agent tool calls to the apply endpoint if they are not essential. Monitor the apply path closely for suspicious activity. These are temporary mitigations—patching is the permanent fix.
This analysis is based on the CVE-2026-53808 official description and CVSS metrics as of the publication date. Verify version numbers, affected products, and patch availability against the official OpenClaw security advisory and vendor release notes before deployment. Organizations should test patches in non-production environments first. Risk scores and impact may vary based on your environment, configuration, and business context. This document does not constitute legal or compliance advice. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-32906MEDIUMOpenClaw Privilege Escalation in Slack Plugin Approvals
- CVE-2026-34507MEDIUMOpenClaw QQBot Admin Command Policy Bypass (CVSS 5.4)
- CVE-2026-35673MEDIUMOpenClaw SSRF Policy Bypass in Debug and Export Routes
- CVE-2026-53835MEDIUMOpenClaw Feishu Dynamic-Agent Binding Authorization Bypass
- CVE-2026-53854MEDIUMOpenClaw Privilege Escalation via Cross-Channel Command Authorization Bypass
- CVE-2026-53860MEDIUMOpenClaw Sender Policy Bypass in BlueBubbles
- CVE-2026-35674HIGHOpenClaw Gateway Scope Bypass Privilege Escalation
- CVE-2026-53807HIGHOpenClaw Telegram Authorization Bypass (CVSS 8.8)