Command approval bypass via reusable BusyBox allowlist
Published Aug 6, 2026 · Updated Aug 6, 2026
Incorrect authorization in OpenClaw-CN openclaw-cn 2026.2.5 allows remote authenticated users to bypass repeat command approval. The gateway's allow-always path stores only the resolved BusyBox executable path, so later busybox sh -c payloads match trust granted to a different command. Exploitation requires gateway exec in allowlist mode with ask-on-miss and one operator approval; the published test reached the trusted execution branch but crashed before the changed payload completed.
Summary
What happened
Incorrect authorization in OpenClaw-CN openclaw-cn 2026.2.5 allows remote authenticated users to bypass repeat command approval. The gateway's allow-always path stores only the resolved BusyBox executable path, so later busybox sh -c payloads match trust granted to a different command. Exploitation requires gateway exec in allowlist mode with ask-on-miss and one operator approval; the published test reached the trusted execution branch but crashed before the changed payload completed.
The record
- CVE
- CVE-2026-19006
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- OpenClaw-CN
- Product
- openclaw-cn
- Classifications
- CWE-285, CWE-863, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2026.2.5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- BusyBox allow-always verification harnessproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo