Summary
OpenClaw: Unicode canonicalization drift in node metadata policy classification could broaden node allowlists
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.
Affected and Patched Versions
- Affected:
<= 2026.2.26 - Patched:
2026.3.1
Impact
This is a policy-bypass issue within the paired-node trust boundary and can expand node command availability beyond intended defaults.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Node metadata canonicalization was hardened against confusables, and unknown platform defaults were made conservative (excluding system.run and system.which unless explicitly allowlisted).
Frequently Asked Questions
- What is GHSA-392F-GGF5-FP3C? GHSA-392F-GGF5-FP3C is a medium-severity security vulnerability in openclaw (npm), affecting versions < 2026.3.1. It is fixed in 2026.3.1.
- Which versions of openclaw are affected by GHSA-392F-GGF5-FP3C? openclaw (npm) versions < 2026.3.1 is affected.
- Is there a fix for GHSA-392F-GGF5-FP3C? Yes. GHSA-392F-GGF5-FP3C is fixed in 2026.3.1. Upgrade to this version or later.
- Is GHSA-392F-GGF5-FP3C exploitable, and should I be worried? Whether GHSA-392F-GGF5-FP3C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-392F-GGF5-FP3C is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-392F-GGF5-FP3C? Upgrade
openclawto 2026.3.1 or later.