Skip to main content
VulnerabilityPublished Updated

CVE-2026-41347: OpenClaw · HTTP operator endpoints lack browser-origin validation in trusted-proxy mode

Affects openclaw-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-41347· Low 2.3

Not known to be exploited · CVSS 2.3 Low : upgrade to 2026.3.31 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
2.3Low
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.02.3
CNA (VulnCheck)CVSS 3.17.1
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.31
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 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.31.

Affected software

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

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.3.31 or later, where the vulnerability is patched. No additional mitigation is required if the upgrade is applied.

Description

OpenClaw CLI versions prior to 2026.3.31 have a vulnerability where HTTP operator endpoints do not validate browser-origin headers in trusted-proxy mode. This can lead to a cross-site request forgery (CSRF) or browser-origin validation gap. The issue is considered medium severity by the maintainer but is rated high based on CVSS 3.1 scoring. The vulnerability depends on deployments using identity-bearing trusted-proxy browsers rather than shared-secret HTTP operator models. A fix is available in version 2026.3.31 and later.

References

Community reviews

Loading reviews…