CVE-2026-53843

描述

### Summary In affected releases, a surviving pairing-scoped session for a device could re-establish node token authority after that node token had been revoked. Revocation should require the device to lose that authority unless it is approved again through the normal pairing flow. This issue affects token revocation and device-role containment. It does not allow unauthenticated device creation. ### Affected configurations This affects deployments where an already paired device keeps a same-device session with pairing-related scope after its node token is revoked. ### Impact A device that should have lost node WebSocket authority could regain it without renewed approval. That weakens revocation as an operator control and can keep node-level access alive longer than intended. The impact is limited to devices that already had a legitimate pairing/session foothold. ### Patched Versions The first stable patched version is `2026.5.26`. ### Mitigations Upgrade to `[email protected]` or later. If a node token was revoked on an older version, restart the gateway and remove/re-pair the affected device to ensure no stale session remains active.

如何修補 CVE-2026-53843

要修補 CVE-2026-53843,請將受影響套件升級到下列已修補版本。

• —升級至 2026.5.26 或更新版本

CVE-2026-53843 正在被利用嗎?

目前沒有被利用訊號。CVE-2026-53843 既不在 CISA KEV 也沒有最新的 EPSS 分數。

受影響套件(1)

• from 0, < 2026.5.26

CVSS 分數

參考連結(4)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-53843
• PATCHgithub.com/openclaw/openclaw
• WEBgithub.com/openclaw/openclaw/security/advisories/GHSA-q99w-vh6v-q3v7
• WEBwww.vulncheck.com/advisories/openclaw-node-token-revocation-bypass-via-pairing-scoped-device-session