Quick answers
- Is CVE-2026-100580 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100580 being exploited in the wild.
- How severe is CVE-2026-100580?
- High severity, with a CVSS score of 8.8, published 26 September 2026.
- Which products and versions are affected?
- Openclaw < 2026.7.1.
- Is there a fix for CVE-2026-100580?
- A patch was published on 2026-09-26: Version 2026.7.1 fixes the case sensitivity handling in the cron tool Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100580 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-100580?
- Check whether you run Openclaw 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 model-facing cron tool improperly handles case sensitivity in payload validation, allowing mixed-case command kinds to bypass agent-facing shell-execution guards before normalization into command jobs. An attacker with the ability to steer tool-enabled agents can create persistent cron jobs executing arbitrary commands with process user privileges. The vulnerability exists only in model-facing cron tool usage; direct CLI and authorized Gateway scheduling are unaffected.
Affected products
- OpenClaw openclaw < 2026.7.1
Timeline
- 2026-09-11: disclosed
- 2026-09-26: advisory
- 2026-09-26: patched: Version 2026.7.1 fixes the case sensitivity handling in the cron tool