OpenClaw: Unicode canonicalization drift in node metadata policy classification could broaden node allowlists
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### Summary A paired node could supply Unicode-confusable `platform` or `deviceFamily` metadata that passed metadata pinning but classified differently for command policy resolution, broadening default node command allowlists. ### Impact This is a policy-bypass issue within the paired-node trust boundary and can expand node command availability beyond intended defaults. ### Fix Node metadata canonicalization was hardened against confusables, and unknown platform defaults were made conservative (excluding `system.run` and `system.which` unless explicitly allowlisted). ### Affected and Patched Versions - Affected: `<= 2026.2.26` - Patched: `2026.3.1`
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | openclaw (npm) | before 2026.3.1 | 2026.3.1 | Patch available | GHSA-392f-ggf5-fp3c |
- openclaw (npm) Vendor— Affected before 2026.3.1 Fixed in 2026.3.1 Patch available GHSA-392f-ggf5-fp3c
Remediation
- Fix · GHSA-392f-ggf5-fp3c openclaw (npm) Fixed in 2026.3.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-392f-ggf5-fp3c
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences