Skip to main content
VulnerabilityPublished Updated

CVE-2026-28475: OpenClaw · Config writes could persist resolved ${VAR} secrets to disk

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 4.8 Medium : upgrade to 2026.2.13 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.2.13
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 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 18 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.2.13.

Affected software

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

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

AI-suggested

Upgrade openclaw to version 2026.2.12 or later, which includes a fix using constant-time token comparison. If immediate upgrade is not possible, restrict network access to the hooks endpoint to trusted sources and rotate the hook token after applying the update.

Description

OpenClaw CLI versions prior to 2026.2.12 use a non-constant-time string comparison for hook tokens, allowing an attacker with network access to the hooks endpoint to potentially infer the token via timing attacks. This requires many requests and is complicated by real-world network latency. The vulnerability has a medium severity score of 4.8. A patch is available in version 2026.2.12.

References

Community reviews

Loading reviews…