CVE-2026-32031: OpenClaw: /api/channels gateway-auth boundary bypass via path canonicalization mismatch
OpenClaw up to 2026.2.25 applies gateway authentication to plugin channel routes only when the raw request path is exactly /api/channels or starts with /api/channels/. A plugin that normalizes paths can still treat an uppercase or percent-encoded variant as a channel route, so the auth guard is skipped. Upgrade openclaw to 2026.2.26.
Published Mar 12, 2026 · Updated Mar 25, 2026 · Analysis Oct 31, 2026
What an attacker can do
The server-http component checks the raw path string before it applies gateway auth. A plugin handler may canonicalize the path first, for example by running decodeURIComponent and then lowercasing. The two disagree on variants. The advisory gives /API/channels/nostr/default/profile and /api/channels%2Fnostr%2Fdefault%2Fprofile. The guard sees neither as a channel route and lets them through. The plugin decodes them to /api/channels/* and serves them.
The bypass depends on a plugin that canonicalizes paths, which is why the CVSS vector sets attack complexity high. An unauthenticated caller who can reach the gateway over the network then reaches plugin channel APIs that should require gateway auth. The advisory rates confidentiality and integrity impact as low each. What an attacker gets depends on the plugin: the example paths point at a Nostr channel profile endpoint. The weakness is authentication bypass using an alternate path (CWE-288).
Who is affected
The npm package openclaw, up to and including 2026.2.25, when a plugin handler decodes or lowercases the request path and the gateway HTTP port is reachable by the attacker.
npm ls -g openclaw
openclaw --versionVulnCheck's write-up says versions before 2026.2.26 are affected.
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.2.25
- Fixed in
- 2026.2.26
- Check
npm ls openclaw
How to fix it
Upgrade to openclaw 2026.2.26 or later.
npm install -g [email protected]The advisory text does not describe the code change or list a workaround. As a precaution, keep the Gateway off untrusted networks until you upgrade, since the flaw requires reaching the HTTP port.
How to tell if you were hit
Search gateway access logs for requests to channel routes in unusual forms: mixed-case /API/channels paths, or paths containing %2F after /api/channels. Any such request that returned a successful response without gateway credentials points to use of the bypass. Compare against requests from your own clients, which should use the exact lowercase path.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
Gateway auth for plugin channel endpoints can be bypassed when path canonicalization differs between the gateway guard and plugin handler routing.
Details
On affected versions, server-http only applies gateway auth when raw requestPath matches exactly:
/api/channels/api/channels/*
If a plugin handler canonicalizes path input (for example decodeURIComponent(pathname).toLowerCase()), requests like:
/API/channels/nostr/default/profile/api/channels%2Fnostr%2Fdefault%2Fprofile
can be interpreted as /api/channels/* by the plugin, while the gateway auth guard is skipped.
Impact
Authentication boundary bypass for plugin channel HTTP routes under canonicalization mismatch conditions. Unauthorized callers may access plugin channel APIs that are expected to require gateway auth.
CWE: CWE-288 (Authentication Bypass Using an Alternate Path or Channel) CVSS: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N (Base 5.3, Moderate)
Credited to tdjackey.
Questions
- Which paths trigger CVE-2026-32031?
The advisory gives /API/channels/nostr/default/profile and /api/channels%2Fnostr%2Fdefault%2Fprofile. A plugin canonicalizes them to /api/channels/*, while the gateway auth guard only matches the exact raw prefix.
- Is every OpenClaw install exposed?
The flaw needs a plugin handler that canonicalizes paths, plus network access to the gateway. Versions up to 2026.2.25 carry the guard mismatch.
- What is the severity?
The advisory rates it Moderate: CVSS 3.1 4.8, with high attack complexity and low confidentiality and integrity impact.
References
Read for this analysis:
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
