# CVE-2026-91836: OpenClaw ClawScan incomplete comparison in static scanner

Source: https://junglewise.ai/threats/cve-2026-91836-openclaw-clawscan-incomplete-comparison-in-static-scanner  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-15. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-91836 · Severity: low · CVSS 2.8 · Published 2026-09-15

OpenClaw ClawScan is a security scanning tool used to analyze code and files for vulnerabilities. A logic flaw in its static scanner component causes it to skip certain files during scanning due to incomplete comparison logic, potentially missing security issues in Python bytecode and specially-named files.

Technologies: [Openclaw ClawScan](https://junglewise.ai/threats/technologies/clawscan). Vendors: [Openclaw](https://junglewise.ai/threats/vendors/openclaw).

## Quick answers

**Is CVE-2026-91836 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-91836 being exploited in the wild.

**How severe is CVE-2026-91836?** 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-91836?** A patch was published on 2026-08-13: Fix committed; version 0.1.7 available Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-91836 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-91836?** 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

The vulnerability is an incomplete comparison with missing factors in the static_scanner.go component's file filtering logic. The flaw allows certain files to bypass the scanner's file-matching rules, affecting the detection of malicious code in Python bytecode and files with specific naming patterns. The attack vector is local, requiring access to the host running ClawScan. An attacker with local access could place malicious code in skipped files to evade security scanning. The issue is fixed in version 0.1.7 (patch 9f6a6fbb9f1137345566d0ab44c73893dfe112fa), which improved file scanning to properly handle skipped-name files and Python bytecode.

## Affected products

- OpenClaw ClawScan up to 0.1.6

## Timeline

- 2026-09-15: disclosed
- 2026-08-13: patched: Fix committed; version 0.1.7 available

## References

- [https://github.com/openclaw/clawscan/](https://github.com/openclaw/clawscan/)
- [https://github.com/openclaw/clawscan/commit/9f6a6fbb9f1137345566d0ab44c73893dfe112fa](https://github.com/openclaw/clawscan/commit/9f6a6fbb9f1137345566d0ab44c73893dfe112fa)

## Related threats

- [OpenClaw ClawScan protection mechanism bypass in static scanner](https://junglewise.ai/threats/cve-2026-110689-a-security-flaw-has-been-discovered-in-openclaw-clawscan-up-to-0)
- [OpenClaw ClawScan file classification bypass in IsBinaryFile](https://junglewise.ai/threats/cve-2026-91835-openclaw-clawscan-file-classification-bypass-in-isbinaryfile)