Skip to main content
VulnerabilityPublished Updated

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

Affects openclawSource GCVE Database

0

Mentioned vulnerabilities

CVSS 6.5 Medium : upgrade to 2026.4.22 when convenient.

Data as of 26 Oct 2026, 15:56 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
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

What to do

Upgrade openclaw to 2026.4.22.

Affected software

ProductAffectedFixed in
npmopenclawAffected
  • <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 fixed version is available starting with OpenClaw 2026.4.22. Until upgrading, operators should restart the affected channel runtime after rotating webhook secrets to ensure old secrets are invalidated. Additional mitigations include maintaining narrow channel and tool allowlists, avoiding sharing a Gateway between mutually untrusted users, and disabling the affected webhook feature when not needed.

Description

OpenClaw versions prior to 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 secret rotation. The vulnerability affects the webhook secret revocation process but does not alter OpenClaw's trusted-operator security model. The impact depends on the operator's configuration and exposure of the affected feature. A fix is available starting with version 2026.4.22.

References

Community reviews

Loading reviews…