CVE-2026-91835 — OpenClaw ClawScan File Classifier static_scanner.go IsBinaryFile interpretation conflict
A vulnerability was detected in OpenClaw ClawScan up to 0.1.6. The impacted element is the function IsBinaryFile of the file internal/runner/static_scanner.go of the component File Classifier. The manipulation results in interpretation conflict. Attacking locally is a requirement. The exploit is now public and may be used. Upgrading to version 0.1.7 is sufficient to resolve this issue. The patch is identified as 04401337b3adb9343bd338b21e5e258bf49ca9c8. You should upgrade the affected component.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- CISA SSVC: exploitation "poc"+5
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Openclaw ClawScan).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 2.4 | CVSS 4.0 | Low | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 0.9 | CVSS 4.0 | Low | — | — | cna@vuldb.com via NIST National Vulnerability Database |
| 2.8 | CVSS 3.1 | Low | 1.3 | 1.4 | cna@vuldb.com via NIST National Vulnerability Database |
| 2.8 | CVSS 3.1 | Low | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 2.8 | CVSS 3.0 | Low | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 1.7 | CVSS 2.0 | Low | 3.1 | 2.9 | cna@vuldb.com via NIST National Vulnerability Database |
| 1.7 | CVSS 2.0 | Low | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N (score shown at the top: cna@vuldb.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · openclaw/clawscan
- SSVC assessment updated
- Record published
- CVSS changed · 2.8
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
9 on the record
- github.com/openclaw/clawscan/pull/43
- github.com/openclaw/clawscan/releases/tag/v0.1.7
- github.com/openclaw/clawscan/commit/04401337b3adb9343bd338b21e5e258bf49ca9c8
- github.com/openclaw/clawscan/
- vuldb.com/submit/933532
- vuldb.com/vuln/404071
- vuldb.com/vuln/404071/cti
- github.com/openclaw/clawscan/issues/42
- vuldb.com/cve/CVE-2026-91835
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-110689 OpenClaw ClawScan Static Scanner runner.go shouldSkipTargetPath protection mechanism 1d
- Low CVE-2026-91836 OpenClaw ClawScan Static Scanner static_scanner.go incomplete comparison with missing factors Sep 15, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-91835 is "OpenClaw ClawScan File Classifier static_scanner.go IsBinaryFile interpretation conflict", rated Low. It affects ClawScan (Openclaw); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 2.8 describes technical severity. EPSS 0.16% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.