CVE-2026-62218

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
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 2026.1.20 before 2026.5.27 contain an authorization bypass vulnerability in the device.pair.approve feature that allows lower-trust callers to bypass role-management checks. Attackers can perform actions requiring stronger authorization by reaching the affected feature through configured input paths.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
16.2%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Jul 17, 2026
Patch available. Sources: github.
generic

OpenClaw 2026.1.20 < 2026.5.27 Authorization Bypass via device.pair.approve | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-authorization-bypass-via-device-pair-approve
github Patch Available

device.pair.approve could bypass role-management checks · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-8v95-qqcm-qp9h

Vendor Advisories for CVE-2026-62218(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 20× in last 7d / 20× 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-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:21 UTCEG score recompute
  4. 2026-07-23 00:20 UTCEG score recompute
  5. 2026-07-23 00:20 UTCGHSA enrichment
  6. 2026-07-22 14:08 UTCEPSS rescore
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:25 UTCEPSS rescore
  9. 2026-07-21 15:25 UTCEPSS rescore
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-18 21:23 UTCEG score recompute
  14. 2026-07-18 21:23 UTCGHSA enrichment
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-17 14:51 UTCEG score recompute
  17. 2026-07-17 14:51 UTCGHSA enrichment
  18. 2026-07-17 06:54 UTCGHSA enrichment
  19. 2026-07-17 00:26 UTCEG score recompute
  20. 2026-07-17 00:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62218?
CVE-2026-62218 is a high vulnerability published on July 17, 2026. OpenClaw 2026.1.20 before 2026.5.27 contain an authorization bypass vulnerability in the device.pair.approve feature that allows lower-trust callers to bypass role-management checks. Attackers can perform actions requiring stronger authorization by reaching the affected feature through configured…
When was CVE-2026-62218 disclosed?
CVE-2026-62218 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62218 actively exploited?
CVE-2026-62218 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-62218?
CVE-2026-62218 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-62218?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62218, 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-62218

Explore →

Is Your Infrastructure Affected by CVE-2026-62218?

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

Start Free Scan →Browse All CVEs