Skip to content
Fencer Intel
high 7.4

CVE-2026-3690 json

OpenClaw Canvas Authentication Bypass Vulnerability

published 8mo ago modified 4mo ago also GHSA-vvjh-f6p9-5vcf , EUVD-2026-21622

cvss
7.4
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

OpenClaw Canvas Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of OpenClaw. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the implementation of the the authentication function for canvas endpoints. The issue results from improper implementation of authentication. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-29311.

Patch / fix

  • npm openclaw 2026.2.19
  • openclaw openclaw 2026.2.19

Is CVE-2026-3690 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
6mo ago

Exploit prediction

0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/openclaw/openclaw/security/advisories/GHSA-vvjh-f6p9-5vcf referenced PoC, tagged "exploit" by a source, unverified
  • zerodayinitiative.com https://www.zerodayinitiative.com/advisories/ZDI-26-228/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 7.4 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm openclaw
<2026.2.19
2026.2.19

Affected products

  • OpenClaw OpenClaw

Classification

Weakness
  • CWE-291 Reliance on IP Address for Authentication

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.