Skip to main content
VulnerabilityPublished Updated

CVE-2026-32004: Openclaw cli · OpenClaw has encoded-path auth bypass in plugin `/api/channels` route classification

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2026.3.2 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.2.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.3.2
Fixed in
  • 2026.3.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade OpenClaw CLI to version 2026.3.2 or later, where this vulnerability is fixed. The patch enforces strict path canonicalization and explicit authentication requirements, eliminating the bypass. No additional mitigations are indicated by the vendor advisory.

Description

OpenClaw CLI versions up to 2026.3.1 contain an authentication bypass vulnerability in the plugin route `/api/channels/*` due to a mismatch in path canonicalization depth. This allows specially encoded alternate-path requests to evade authentication checks while still resolving to protected routes. The issue is fixed in version 2026.3.2 with improved canonicalization and stricter auth enforcement.

References

Community reviews

Loading reviews…