Skip to main content
VulnerabilityPublished Updated

CVE-2026-35634: OpenClaw · Gateway Canvas local-direct requests bypass Canvas HTTP and WebSocket authentication

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 2026.3.24 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.24
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA: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.24.

Affected software

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

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.23 or later, which includes the fix requiring authentication for Canvas routes. The fix is contained in the released tags v2026.3.23 and v2026.3.23-2 and the corresponding npm package versions. No additional mitigation is required once updated.

Description

A vulnerability in openclaw-cli before version 2026.3.23 allowed local-direct loopback requests to bypass Canvas HTTP and WebSocket authentication. This occurred because the authorization function treated local-direct requests as automatically authorized without verifying bearer tokens or capabilities. The issue was fixed in version 2026.3.23 by requiring authentication for Canvas routes.

References

Community reviews

Loading reviews…