CVE-2026-32027

DM pairing-store identities were incorrectly eligible for group allowlist authorization checks, enabling cross-context authorization in group message paths.

Details

In affected versions, group allowlist evaluation could inherit identities from the DM pairing store. A sender approved via DM pairing could satisfy group sender allowlist checks without being explicitly present in groupAllowFrom.

This is an authorization-policy boundary issue between DM pairing and group allowlists.

Affected Packages / Versions

• openclaw (npm): affected <= 2026.2.25 (latest published npm version at triage time)
• openclaw (npm): patched >= 2026.2.26 (planned next release)

Fix Commit(s)

• openclaw/openclaw@8bdda7a651c21e98faccdbbd73081e79cffe8be0
• openclaw/openclaw@051fdcc428129446e7c084260f837b7284279ce9

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.26) so once npm release is published, maintainers can publish the advisory without additional metadata edits.

Maintainer Timeline Note

Maintainers landed the initial fix before this report was filed; this report still provided useful independent confirmation of the issue class and exploit path.

OpenClaw thanks @tdjackey for reporting.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-32027 has a CVSS score of 6.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.26); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-32027? CVE-2026-32027 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions <= 2026.2.25. It is fixed in 2026.2.26. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-32027? CVE-2026-32027 has a CVSS score of 6.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32027? openclaw (npm) versions <= 2026.2.25 is affected.
4. Is there a fix for CVE-2026-32027? Yes. CVE-2026-32027 is fixed in 2026.2.26. Upgrade to this version or later.
5. Is CVE-2026-32027 exploitable, and should I be worried? Whether CVE-2026-32027 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
6. What actually determines whether CVE-2026-32027 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.
7. How do I fix CVE-2026-32027? Upgrade openclaw to 2026.2.26 or later.