CVE-2026-53843

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-16. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OpenClaw 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.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
19.3%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 18, 2026

Advisory Details (2)

Auto-updated Jun 16, 2026
Patch available. Sources: github.
generic

OpenClaw < 2026.5.26 - Node Token Revocation Bypass via Pairing-Scoped Device Session | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-node-token-revocation-bypass-via-pairing-scoped-device-session
github Patch Available

Pairing-scoped device session could restore revoked node token authority · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-q99w-vh6v-q3v7

Vendor Advisories for CVE-2026-53843(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
openclaw—2026.5.26—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 74× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 23:07 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 21:44 UTCEG score recompute
  7. 2026-07-05 09:35 UTCEG score recompute
  8. 2026-07-05 02:31 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 21:26 UTCEG score recompute
  11. 2026-07-04 09:08 UTCEG score recompute
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-03 14:16 UTCEG score recompute
  15. 2026-07-03 02:04 UTCEG score recompute
  16. 2026-07-02 13:54 UTCEG score recompute
  17. 2026-07-02 01:45 UTCEG score recompute
  18. 2026-07-01 15:07 UTCEPSS rescore
  19. 2026-07-01 13:36 UTCEG score recompute
  20. 2026-07-01 01:27 UTCEG score recompute
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 13:13 UTCEG score recompute
  23. 2026-06-30 01:03 UTCEG score recompute
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 49 more
  1. 2026-06-29 12:54 UTCEG score recompute
  2. 2026-06-29 00:45 UTCEG score recompute
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 12:35 UTCEG score recompute
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 00:26 UTCEG score recompute
  8. 2026-06-27 12:11 UTCEG score recompute
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-26 23:59 UTCEG score recompute
  11. 2026-06-26 11:50 UTCEG score recompute
  12. 2026-06-25 23:42 UTCEG score recompute
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-25 11:30 UTCEG score recompute
  15. 2026-06-24 23:20 UTCEG score recompute
  16. 2026-06-24 14:05 UTCEPSS rescore
  17. 2026-06-24 11:11 UTCEG score recompute
  18. 2026-06-23 23:02 UTCEG score recompute
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-23 10:53 UTCEG score recompute
  22. 2026-06-22 22:41 UTCEG score recompute
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-22 10:32 UTCEG score recompute
  26. 2026-06-21 22:03 UTCEG score recompute
  27. 2026-06-21 14:56 UTCEPSS rescore
  28. 2026-06-21 14:56 UTCEPSS rescore
  29. 2026-06-21 09:51 UTCEG score recompute
  30. 2026-06-21 01:59 UTCEPSS rescore
  31. 2026-06-21 01:59 UTCEPSS rescore
  32. 2026-06-20 21:42 UTCEG score recompute
  33. 2026-06-20 09:31 UTCEG score recompute
  34. 2026-06-19 21:20 UTCEG score recompute
  35. 2026-06-19 19:26 UTCEPSS rescore
  36. 2026-06-19 19:26 UTCEPSS rescore
  37. 2026-06-19 08:58 UTCEG score recompute
  38. 2026-06-18 20:30 UTCEG score recompute
  39. 2026-06-18 17:52 UTCEPSS rescore
  40. 2026-06-18 17:52 UTCEPSS rescore
  41. 2026-06-18 08:21 UTCEG score recompute
  42. 2026-06-18 08:21 UTCGHSA enrichment
  43. 2026-06-17 20:08 UTCEG score recompute
  44. 2026-06-17 20:08 UTCGHSA enrichment
  45. 2026-06-17 17:53 UTCEPSS rescore
  46. 2026-06-17 07:59 UTCEG score recompute
  47. 2026-06-17 07:59 UTCGHSA enrichment
  48. 2026-06-16 19:50 UTCEG score recompute
  49. 2026-06-16 19:48 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53843?
CVE-2026-53843 is a high vulnerability published on June 16, 2026. OpenClaw 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…
When was CVE-2026-53843 disclosed?
CVE-2026-53843 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53843 actively exploited?
CVE-2026-53843 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53843?
CVE-2026-53843 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-53843?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53843, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53843

Explore →

Is Your Infrastructure Affected by CVE-2026-53843?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs