Quick answers
- Is CVE-2026-91835 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91835 being exploited in the wild.
- How severe is CVE-2026-91835?
- Low severity, with a CVSS score of 2.8, published 15 September 2026.
- Which products and versions are affected?
- Openclaw ClawScan up to 0.1.6.
- Is there a fix for CVE-2026-91835?
- A patch was published on 2026-08-14: Patch commit 04401337b3adb9343bd338b21e5e258bf49ca9c8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-91835 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-91835?
- Check whether you run Openclaw ClawScan 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
A logic error in the IsBinaryFile function of internal/runner/static_scanner.go allows bypassing content scanning through NUL byte interpretation conflicts. An attacker with local filesystem access can craft files with embedded NUL characters that are misclassified as binary, preventing the scanner from analyzing their actual content. The vulnerability requires local file system manipulation and does not affect remote scanning operations. A patch is available in version 0.1.7 (commit 04401337b3adb9343bd338b21e5e258bf49ca9c8).
Affected products
- OpenClaw ClawScan up to 0.1.6
Timeline
- 2026-09-15: disclosed
- 2026-08-14: patched: Patch commit 04401337b3adb9343bd338b21e5e258bf49ca9c8