Skip to main content
VulnerabilityPublished Updated

CVE-2026-43585: OpenClaw · Gateway HTTP endpoints re-resolve bearer auth after SecretRef rotation

Affects openclaw-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-43585· Critical 9.2

Not known to be exploited · CVSS 9.2 Critical : upgrade to 2026.4.15 as a priority.

Data as of 17 Nov 2026, 20:25 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 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.15.

Affected software

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

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.4.15 that addresses this issue by dynamically resolving bearer authentication per request and upgrade. Users should upgrade to version 2026.4.15 or later to ensure that bearer tokens are properly invalidated after SecretRef rotation.

Description

OpenClaw CLI versions prior to 2026.4.15 have a vulnerability where the gateway HTTP and WebSocket handlers cache bearer token authentication at startup. After a SecretRef rotation intended to revoke old tokens, the gateway could continue accepting the old bearer token until the process is restarted. This allows an old token to remain valid longer than intended, posing a high security risk. The issue is fixed in version 2026.4.15 by re-resolving bearer authentication from the current runtime secret snapshot on each request and WebSocket upgrade.

References

Community reviews

Loading reviews…