<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rce on CuraSec</title><link>https://curasec.metacog.co.kr/tags/rce/</link><description>Recent content in Rce on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Jul 2026 09:49:54 -0500</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/rce/index.xml" rel="self" type="application/rss+xml"/><item><title>Three Patched OpenClaw AI Assistant Flaws Enable Host Takeover via WhatsApp</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-researcher-details-whatsapp-to-host-attack-chain-using-three/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-researcher-details-whatsapp-to-host-attack-chain-using-three/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If OpenClaw is deployed in your environment, verify you are running a patched version addressing all three CVEs (GHSA-hjr6-g723-hmfm and siblings); no public PoC or KEV listing present, so patch within normal cycle but prioritize given CVSS 8.8 and the RCE/privilege-escalation chain.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No published IOCs or active exploitation reported; the attack chain description (WhatsApp input → credential theft → privilege escalation → host RCE) is worth understanding to recognize behavioral indicators if OpenClaw is in scope, but no detection work is actionable today.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>