Skip to main content
VulnerabilityPublished Updated

CVE-2026-41299: OpenClaw · Gateway chat.send ACP-only provenance guard could be bypassed by client identity spoofing

Affects openclaw-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-41299· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 2026.3.28 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.1
CNA (VulnCheck)CVSS 3.17.1
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.28
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Apr 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.28.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <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 fix is available in OpenClaw CLI version 2026.3.28 and later. Users should upgrade to this version or newer to ensure the vulnerability is remediated.

Description

OpenClaw CLI had a vulnerability in its chat.send gateway where ACP-only provenance fields were controlled by self-declared client metadata from the WebSocket handshake instead of verified authorization. This allowed authenticated operator clients to spoof ACP identity labels and inject reserved provenance fields meant only for the ACP bridge. The issue was fixed in version 2026.3.28.

References

Community reviews

Loading reviews…