Quick answers
- Is CVE-2026-101882 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101882 being exploited in the wild.
- How severe is CVE-2026-101882?
- High severity, with a CVSS score of 8.8, published 30 September 2026.
- Which products and versions are affected?
- Openclaw Windows Node before 2026.7.1.
- Is there a fix for CVE-2026-101882?
- A patch was published on 2026-07-20: Fix merged requiring concrete executable patterns without wildcards Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-101882 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-101882?
- Check whether you run Openclaw Windows Node at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The system.execApprovals.set method in OpenClaw Windows Node before 2026.7.1 fails to properly validate executable allow patterns, accepting wildcards and dangerous system binaries (mshta, rundll32, certutil) that can match nearly any command through glob matching. Remote callers can invoke system.run to execute arbitrary commands with these over-permissive rules already in place, bypassing operator checks and user prompts. The fix requires concrete executable names without wildcards in allow patterns.
Affected products
- OpenClaw Windows Node before 2026.7.1
Timeline
- 2026-09-30: disclosed
- 2026-07-20: patched: Fix merged requiring concrete executable patterns without wildcards