CVE-2026-53843
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenClaw before 2026.5.26 contains an authorization bypass vulnerability where a surviving pairing-scoped device session can re-establish node token authority after revocation. Attackers with a paired device can regain WebSocket node-level access without renewed approval, weakening revocation controls and maintaining unauthorized access longer than intended.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpenClaw before 2026.5.26 has an authorization bypass where a pairing-scoped device session survives revocation and can re-establish node token authority. Attackers with an existing paired device can regain WebSocket node-level access without renewed approval by leveraging this surviving session to re-authenticate, effectively bypassing revocation controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.5.26= 2026.5.26CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify OpenClaw versionCheck the installed OpenClaw version against the affected ranges (< 2026.5.26 or = 2026.5.26). Consult your system's package manager, software inventory, or the application's about/version page.Affected if The installed version is any version before 2026.5.26, or exactly 2026.5.26.
-
Confirm WebSocket node token feature is enabledInspect the OpenClaw configuration files or runtime settings to determine whether the WebSocket node token authority feature is active. Look for settings related to WebSocket connections, node authentication, or token-based session management.Affected if WebSocket node token feature is enabled and in use.
-
Identify existing device pairing sessionsReview active or recently active device pairing records in the OpenClaw system. Check session management logs, database, or admin console for devices that were previously paired. Note their session states (active, revoked, expired).Affected if There are existing device pairing sessions that may have been previously revoked.
-
Review session revocation behaviorTest or inspect the session revocation mechanism by attempting to revoke a device pairing and observing whether a previously paired device can reconnect or regain node-level access without re-authentication. Check revocation audit logs for unexpected re-authorization events.Affected if Revoked device sessions can reconnect or regain node-level access without renewed approval.
A user is affected if they run any OpenClaw version before 2026.5.26 (or exactly 2026.5.26), have the WebSocket node token feature enabled, and have device pairing sessions where revocation can be bypassed to regain access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2026.5.26
Update to OpenClaw 2026.5.26 or later. Additionally, review and ensure complete invalidation of all session types (device-pairing scoped and node-level) during revocation to prevent token authority re-establishment.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53843 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53843 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data