CVE-2026-53830
mediumpriority · track · 0EPSS 0.002 · 11 %ileDEEUUSEPSS · scored 2026-10-27
OpenClaw before 2026.4.22 contains a webhook secret revocation bypass vulnerability allowing callers with old Slack and Zalo webhook secrets to remain active after secrets.reload. Attackers can exploit the stale-secret window to deliver webhook events after operator-expected secret revocation, potentially accepting previous credentials.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 2.3–6.5
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (5)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-1913OpenClaw: Mehrere Schwachstellen ermöglichen die Umgehung von SicherheitsmaßnahmenDeutsch2026-06-14csaf · cert_bundDE
Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um Sicherheitsmaßnahmen zu umgehen und so Daten zu manipulieren oder beliebigen Code auszuführen.
- GHSA-275c-xpvc-jgfwOpenClaw: Slack and Zalo webhook secrets could remain active after secrets.reload2026-07-02ghsa · osvUS
### Summary Slack and Zalo webhook secrets could remain active after secrets.reload. In affected versions, a caller with an old webhook secret during the stale-secret window could keep accepting the previous secret after `secrets.reload`. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabled and reachable, this could deliver webhook events briefly after the operator expected revocation. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path. ### Patched Versions The first stable patched version is `2026.4.22`. ### Mitigations restart the affected channel runtime after rotating webhook secrets until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (7)
External citations — patches, advisories, analysis.
- https://github.com/openclaw/openclaw/releasesPatchcnnvd
- https://github.com/openclaw/openclaw/security/advisories/GHSA-275c-xpvc-jgfwcnnvd
- https://www.vulncheck.com/advisories/openclaw-webhook-secret-revocation-bypass-via-secrets-reloadcnnvd
- https://github.com/openclaw/openclaw/security/advisories/GHSA-275c-xpvc-jgfwenisa_euvd
- https://www.vulncheck.com/advisories/openclaw-webhook-secret-revocation-bypass-via-secrets-reloadenisa_euvd
- https://github.com/openclaw/openclaw/security/advisories/GHSA-275c-xpvc-jgfwMitigationVendor Advisorynvd
- https://www.vulncheck.com/advisories/openclaw-webhook-secret-revocation-bypass-via-secrets-reloadThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan