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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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

Published by the source

2 Mar 2026, 21:49 UTC

Last modified by the source

4 Mar 2026, 15:10 UTC

Source last checked

26 Oct 2026, 12:42 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-392f-ggf5-fp3c

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-392f-ggf5-fp3c

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-392f-ggf5-fp3c

Advisory: OpenClaw: Unicode canonicalization drift in node metadata policy classification could broaden node allowlists
IDs: GHSA-392f-ggf5-fp3c
Record: https://patchnext.com/advisories/ghsa-392f-ggf5-fp3c (revision 3, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm openclaw: affected < 2026.3.1; fixed in 2026.3.1

## Suggested inspection (read-only)
- `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openclaw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-392f-ggf5-fp3c (OSV record GHSA-392f-ggf5-fp3c lists affected ranges: npm openclaw >=0 <2026.3.1 (fixed))
- Verified: https://github.com/advisories/GHSA-392f-ggf5-fp3c (GitHub-reviewed advisory GHSA-392f-ggf5-fp3c lists affected ranges: npm openclaw >=0 <2026.3.1)

Commands are suggestions: review each one before running it.