Skip to main content
VulnerabilityPublished Updated

CVE-2026-43535: OpenClaw · Collect-mode queue batches could reuse the last sender authorization context

Affects openclaw-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-43535· High 7.6

Not known to be exploited · CVSS 7.6 High : upgrade to 2026.4.14 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.4.14
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 May 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.4.14.

Affected software

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

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

AI-suggested

Users should upgrade to openclaw-cli version 2026.4.14 or later, which includes the official fix for this vulnerability. The fix is included in the npm release 2026.4.14. No additional mitigation steps are required once the upgrade is applied.

Description

A vulnerability in openclaw-cli versions before 2026.4.14 allows collect-mode queue batches to reuse the last sender's authorization context. This causes messages from different senders to be processed with the authorization context of the final sender in the batch, potentially granting earlier messages elevated privileges. The issue is fixed in version 2026.4.14 by ensuring batches are split by sender authorization context before dispatch.

References

Community reviews

Loading reviews…