Skip to content
Applications

CVE-2026-62200

8.7
High
EPSS 0.53%Patch availableJul 14, 2026

OpenClaw flaw allows low-trust callers to abuse Git external transport for unauthorized actions.

common questions

Is CVE-2026-62200 being exploited?

Not confirmed. CVE-2026-62200 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.53% probability of exploitation in the next 30 days.

How severe is CVE-2026-62200?

CVE-2026-62200 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-62200?

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

What does CVE-2026-62200 affect?

CVE-2026-62200 affects OpenClaw < 2026.6.1, OpenClaw host exec environment with Git external transport enabled, Systems exposing OpenClaw Git ext transport. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62200?

Upgrade to OpenClaw 2026.6.1 or disable Git external transport until patched.

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

executive summary
technical analysis
affected
OpenClaw < 2026.6.1OpenClaw host exec environment with Git external transport enabledSystems exposing OpenClaw Git ext transport
impact

Low-trust caller can execute commands or persist actions via Git external transport, bypassing host exec environment filters.

action required

Immediate action required

affected versions
OpenClaw OpenClaw
  • affected< 2026.6.6
vendor says fixed in2026.6.6

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