Skip to main content
VulnerabilityPublished Updated

CVE-2026-27646: OpenClaw · Sandboxed /acp spawn requests could initialize host ACP sessions

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 2026.3.7 when convenient.

Data as of 19 Nov 2026, 19:34 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.7
CVSS:3.1/AV:L/AC:L/PR:L/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 18 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.7.

Affected software

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

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 in openclaw-cli version 2026.3.7 and later. Users should upgrade to this version or newer to ensure the vulnerability is fixed. The fix enforces proper runtime-policy guards on the /acp spawn command to prevent sandboxed sessions from initializing host ACP sessions. No additional mitigation is required once patched.

Description

A vulnerability in the openclaw-cli npm package versions up to 2026.3.2 allows sandboxed requester sessions to initialize host-side ACP sessions via the /acp spawn command. This occurs because the command path did not enforce the same runtime guard as other ACP spawn requests, enabling sandboxed sessions to cross into host-side ACP runtime initialization. The issue is fixed in version 2026.3.7 by adding a shared ACP runtime-policy guard to prevent unauthorized ACP session initialization from sandboxed contexts.

References

Community reviews

Loading reviews…