CVE-2026-32004

Summary (Updated March 2, 2026)

Encoded alternate-path requests could bypass plugin route auth checks for /api/channels/* due to canonicalization depth mismatch in vulnerable builds.

Affected Packages / Versions

• Package: openclaw (npm)
• Latest published vulnerable version: 2026.3.1
• Affected range: <= 2026.3.1
• Patched release: 2026.3.2 (patched_versions: >= 2026.3.2)

Technical Details

In affected versions, plugin auth-path classification and route-path canonicalization could diverge for deeply encoded slash variants (for example multi-encoded %2f). That mismatch allowed alternate encoded paths to evade protected-prefix auth checks while still resolving to /api/channels/... in plugin route handling.

The fix set hardens this class of issue by:

• canonicalizing route paths to a bounded fixpoint,
• failing closed on malformed or unresolved canonicalization depth,
• requiring explicit plugin-route auth contracts (no implicit auth default),
• enforcing route ownership/conflict guards for duplicate route registrations, and
• using shared webhook route lifecycle registration to avoid stale/conflicting route surfaces.

Affected Deployments

Deployments exposing plugin HTTP routes and relying on gateway auth for /api/channels/* protection.

Fix Commit(s)

• 93b07240257919f770d1e263e1f22753937b80ea
• 2fd8264ab03bd178e62a5f0c50d1c8556c17f12d
• d74bc257d8432f17e50b23ae713d7e0623a1fe0f
• 7a7eee920a176a0043398c6b37bf4cc6eb983eeb

CVE-2026-32004 has a CVSS score of 6.5 (High). The vector is network-reachable, no 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.3.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-32004? CVE-2026-32004 is a high-severity security vulnerability in openclaw (npm), affecting versions <= 2026.3.1. It is fixed in 2026.3.2.
2. How severe is CVE-2026-32004? CVE-2026-32004 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-32004? openclaw (npm) versions <= 2026.3.1 is affected.
4. Is there a fix for CVE-2026-32004? Yes. CVE-2026-32004 is fixed in 2026.3.2. Upgrade to this version or later.
5. Is CVE-2026-32004 exploitable, and should I be worried? Whether CVE-2026-32004 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-32004 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-32004? Upgrade openclaw to 2026.3.2 or later.