Skip to main content
VulnerabilityPublished Updated

CVE-2026-53830: OpenClaw · Slack and Zalo webhook secrets could remain active after secrets.reload

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2026.4.22 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
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.4.22
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 16 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.4.22.

Affected software

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

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.22. Until patched, operators should restart the affected channel runtime after rotating webhook secrets to ensure old secrets are fully revoked. Additionally, operators should keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when not needed.

Description

OpenClaw CLI versions from 2026.1.29 up to but not including 2026.4.22 have a vulnerability where Slack and Zalo webhook secrets may remain active after a secrets.reload operation. This allows a caller with an old webhook secret to continue sending webhook events during a brief stale-secret window after revocation. The issue affects only the named feature and does not alter the trusted-operator security model. The vulnerability has a medium severity rating with a CVSS score of 6.5. A patch is available starting from version 2026.4.22. Operators are advised to restart the affected channel runtime after rotating webhook secrets as a mitigation until they apply the patch.

References

Community reviews

Loading reviews…