Skip to main content
VulnerabilityPublished Updated

CVE-2026-41407: OpenClaw · Shared-secret comparison call sites leaked length information through timing

Affects openclaw-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-41407· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2026.4.2 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

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

Affected software

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

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 version 2026.4.2 and later, which reuses the shared secret comparison helper to ensure constant-time secret comparisons. Users should upgrade to version 2026.4.2 or newer to remediate this issue.

Description

OpenClaw CLI versions before 2026.4.2 contained a timing side channel vulnerability in shared-secret comparison call sites. The issue arose because some code paths used early length-mismatch checks instead of a constant-time fixed-length comparison helper, leaking secret length information through timing differences. This vulnerability has low severity and does not directly allow authentication bypass. The flaw was fixed in version 2026.4.2 by reusing the shared secret comparison helper consistently.

References

Community reviews

Loading reviews…