Skip to content
IoT

CVE-2026-62218

8.7
High
EPSS 0.45%Patch availableJul 17, 2026

Auth bypass in OpenClaw device.pair.approve allows lower-trust callers to perform privileged actions

common questions

Is CVE-2026-62218 being exploited?

Not confirmed. CVE-2026-62218 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.

How severe is CVE-2026-62218?

CVE-2026-62218 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-62218?

Yes. A fix has been recorded for CVE-2026-62218. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-62218 affect?

CVE-2026-62218 affects OpenClaw < 2026.5.27, OpenClaw 2026.1.20, device.pair.approve feature. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62218?

Upgrade to OpenClaw 2026.5.27+, restrict access to device.pair.approve, and audit role changes.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OpenClaw < 2026.5.27OpenClaw 2026.1.20device.pair.approve feature
impact

Bypasses role checks to approve device pairings, grant roles, escalate privileges, and enable device/system takeover.

action required

Patch when possible

affected versions
OpenClaw OpenClaw
  • affected>= 2026.1.20 and < 2026.5.27
vendor says fixed in2026.5.27

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free