Skip to main content
VulnerabilityPublished Updated

CVE-2026-35636: OpenClaw · `session_status` sessionId resolution bypasses sandboxed session-tree visibility

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 2026.3.28 soon.

Data as of 17 Nov 2026, 20:25 UTC

Severity
High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.28

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 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.28.

Affected software

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

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

AI-suggested

A patch is available and was introduced in openclaw-cli version 2026.3.25. Users should upgrade to version 2026.3.25 or later to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in openclaw-cli versions 2026.3.11 through 2026.3.24 allows sandboxed sessions to bypass intended session-tree visibility restrictions via the session_status sessionId resolution. This flaw permits sandboxed child sessions to access parent or sibling sessions that should be blocked. The issue was fixed in version 2026.3.25 by enforcing visibility checks after sessionId resolution.

References

Community reviews

Loading reviews…