Skip to content
Fencer Intel
medium —

GHSA-392f-ggf5-fp3c json

OpenClaw: Unicode canonicalization drift in node metadata policy classification could broaden node allowlists

published 8mo ago modified 8mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

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`

Patch / fix

  • npm openclaw 2026.3.1

Is GHSA-392f-ggf5-fp3c in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
npm openclaw
<2026.3.1
2026.3.1

Classification

Weakness
  • CWE-176 Improper Handling of Unicode Encoding
  • CWE-436 Interpretation Conflict

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of openclaw/openclaw published their own advisory on GitHub. Reviewed sources take precedence over it.