CVE-2026-53817

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:vulncheck, epss
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.22 contains a locality validation vulnerability in Control UI pairing that allows attackers with network access to spoof locality information and obtain durable admin-capable device tokens. Attackers can exploit insufficient locality-derived trust validation to convert temporary shared access into persistent administrative credentials that survive token rotation.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
22.7%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 23, 2026

Advisory Details (2)

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

OpenClaw < 2026.5.22 - Control UI Locality Spoofing in Device Pairing | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-control-ui-locality-spoofing-in-device-pairing
github Patch Available

Control UI locality spoofing could mint a durable admin device token · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-chr9-m4q2-76hw

Vendor Advisories for CVE-2026-53817(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-53817?
CVE-2026-53817 is a high vulnerability published on June 11, 2026. OpenClaw before 2026.5.22 contains a locality validation vulnerability in Control UI pairing that allows attackers with network access to spoof locality information and obtain durable admin-capable device tokens. Attackers can exploit insufficient locality-derived trust validation to convert…
When was CVE-2026-53817 disclosed?
CVE-2026-53817 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53817 actively exploited?
CVE-2026-53817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53817?
CVE-2026-53817 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53817?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53817, 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

Explore the affected products and dependency analysis for CVE-2026-53817

Explore →

Is Your Infrastructure Affected by CVE-2026-53817?

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

Start Free Scan →Browse All CVEs