A public exploit is now circulating for a critical vulnerability in AnyDesk for Linux that lets an attacker run commands as root on a remote machine before the user ever approves the session. The flaw, tracked as CVE-2026-109390 and dubbed AnyPwn by the researchers who found it, carries a CVSS score of 9.8 out of 10. If you run AnyDesk on Linux, the fix is straightforward: update to version 8.0.3 or newer now.
What Is the AnyDesk AnyPwn Vulnerability?
AnyPwn is a pre-authentication remote code execution flaw in the session protocol of AnyDesk for Linux. In practical terms, it means an attacker can connect to a target machine over the network and execute commands with full root privileges without needing any credentials and without waiting for the victim to accept the connection.
The root cause sits in the way AnyDesk’s session handler processes incoming stream packets. It trusts a length value supplied by the remote side before validating it. When the software allocates memory, 32-bit arithmetic on an oversized length value wraps around to a very small number, so AnyDesk reserves a small buffer while continuing to treat the incoming data as its original large size. Copying the packet bytes then writes past the end of the buffer, corrupting heap memory, and that corruption is what the exploit converts into command execution.
Who Found It and When Was It Disclosed?
The flaw was found by Rick de Jager of the V12 security research team. V12 first announced AnyPwn on June 22, 2026, and AnyDesk acknowledged the report the following day. The team published the full proof-of-concept exploit code publicly on October 8, 2026. The CVE identifier, CVE-2026-109390, was assigned on October 12, 2026, along with the 9.8 critical severity rating.
That timeline matters: there was a responsible disclosure window of several months during which AnyDesk shipped a fix, but the release of a working public exploit means unpatched systems are now at real risk.
Which Versions Are Affected?
According to the researchers, the public exploit targets AnyDesk for Linux version 8.0.2. Earlier builds such as 8.0.1 are suspected to share the same vulnerable code, though that has not been confirmed.
The vulnerability is fixed in AnyDesk 8.0.3 and later. Version 8.1.0 is the current release. The flaw appears specific to the Linux build; there is no indication it affects the Windows or macOS clients.
How Serious Is It?
Several factors make this one worse than a typical desktop software bug:
- No authentication required. The attack works before any user approval prompt, so there is no human in the loop to stop it.
- Root-level access. On Linux, the AnyDesk service commonly runs as root, so a successful exploit hands over full system control.
- Two attack paths. The proof of concept works over a direct TCP connection on port 7070, and the researchers say the same vulnerable path is also reachable through AnyDesk’s relay connections, which means a firewall that blocks direct inbound traffic does not fully eliminate exposure.
- Public exploit code. Anyone can now study, adapt, and automate the attack.
No in-the-wild exploitation has been confirmed as of October 13, 2026, but with working code in the open, that could change quickly. The good news is that defenders have a clear patch to deploy.
What You Should Do Right Now
If AnyDesk is installed on any Linux system you manage, take these steps today:
- Update AnyDesk to 8.0.3 or later. This is the single most important step and it closes the vulnerability completely.
- Restrict inbound access to TCP port 7070 with firewall rules so only trusted sources can reach the AnyDesk service directly.
- Limit AnyDesk exposure to trusted networks only. If the machine does not need to be reachable from the internet, make sure it is not.
- Avoid running the AnyDesk service as root where your setup allows it, to reduce the blast radius if something similar surfaces again.
For administrators, it is worth checking your inventory for any Linux endpoints still running 8.0.2 or earlier and pushing the update through your normal software deployment tooling rather than relying on users to update manually.
How This Fits Into a Broader Pattern
Remote access tools are attractive targets because they are already designed to control machines from afar, and a flaw in one effectively hands attackers a ready-made backdoor. AnyDesk’s AnyPwn is far from the first example. Researchers recently disclosed a one-click account takeover flaw in Telegram Desktop (CVE-2026-107181) that chained message-link handling bugs to steal session files, and enterprise remote access appliances keep appearing in the headlines too, from the Citrix NetScaler SAML zero-day to the SonicWall SMA 1000 flaw that drew 135 exploitation attempts within days of disclosure.
The lesson repeats itself: keep remote access software patched, minimize its network exposure, and treat it as privileged infrastructure rather than just another utility on the desktop.
Frequently Asked Questions
What is CVE-2026-109390?
CVE-2026-109390 is a critical pre-authentication remote code execution vulnerability in AnyDesk for Linux, nicknamed AnyPwn. It has a CVSS score of 9.8 and lets a remote attacker run commands as root before the user approves the session.
Is AnyDesk safe to use on Linux now?
Yes, provided you update. The flaw is fixed in AnyDesk 8.0.3 and later, with 8.1.0 as the current release. Versions 8.0.2 and possibly earlier are vulnerable. Windows and macOS clients are not reported to be affected.
Can this vulnerability be exploited over the internet?
The proof of concept works over a direct TCP connection on port 7070, and the researchers say the vulnerable code path is also reachable via AnyDesk relay connections. Machines reachable from the internet are at higher risk, which is why firewall rules and network segmentation matter even after patching.
Has the AnyPwn exploit been used in real attacks?
As of October 13, 2026, there is no confirmed report of the exploit being used in the wild. However, the exploit code is public, so exploitation is likely only a matter of time for unpatched systems.
What should I do if I can’t update AnyDesk immediately?
Until you can update, block inbound TCP port 7070 at your firewall, keep the machine on a trusted network only, and consider stopping the AnyDesk service entirely on internet-exposed systems. Patching as soon as possible remains the only complete fix.