<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Anydesk on CuraSec</title><link>https://curasec.metacog.co.kr/tags/anydesk/</link><description>Recent content in Anydesk on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 09 Oct 2026 17:26:04 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/anydesk/index.xml" rel="self" type="application/rss+xml"/><item><title>Working Pre-Auth Root RCE Exploit Published for AnyDesk Linux</title><link>https://curasec.metacog.co.kr/insights/2026-10-09-researchers-publish-working-exploit-for-pre-auth-anydesk-lin/</link><pubDate>Fri, 09 Oct 2026 17:26:04 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-09-researchers-publish-working-exploit-for-pre-auth-anydesk-lin/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> A public working exploit for a pre-auth root RCE means active exploitation risk is immediate; upgrade AnyDesk Linux to version 8.0.3 on all hosts and audit for any instances still running older versions.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> No IOCs or active campaign reported yet, but working exploit publication typically precedes mass exploitation; build or tune detections for anomalous process spawning from the AnyDesk daemon on Linux endpoints and queue a hunt for lateral movement from remote-access tools.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Confirm whether AnyDesk Linux is deployed in the environment and verify the patch is applied; the vendor&amp;rsquo;s deliberately vague changelog — no CVE, no security advisory — is a vendor-transparency red flag worth raising in your next vendor risk review.&lt;/li>
&lt;/ul></description></item></channel></rss>