PatchSiren cyber security CVE debrief
CVE-2026-109390 AnyDesk CVE debrief
CVE-2026-109390 is a critical vulnerability in AnyDesk before version 8.0.3, allowing unauthenticated remote attackers to execute arbitrary code via a heap-based buffer overflow. This issue was demonstrated on Linux for command execution as root without the victim approving desktop control. The vulnerability is due to a lack of validation for the payload length value in the stream packet handler for mode 5 in the session protocol.
- Vendor
- AnyDesk
- Product
- Unknown
- CVSS
- CRITICAL 9.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-12
- Original CVE updated
- 2026-10-12
- Advisory published
- 2026-10-12
- Advisory updated
- 2026-10-12
Who should care
System administrators, security teams, and IT professionals responsible for managing and securing AnyDesk installations should assess exposure and prioritize patching to mitigate potential risks.
Why it matters
CVE-2026-109390 is a critical vulnerability in AnyDesk that allows unauthenticated remote code execution. System administrators and security teams should assess exposure and prioritize patching to mitigate potential risks.
- Potential for remote code execution as root on Linux systems
- Unauthenticated exploitation possible
- High CVSS score indicating critical severity
- Requires verification of exposure and patching to version 8.0.3 or later
Technical summary
The vulnerability is caused by a heap-based buffer overflow in the stream packet handler for mode 5 in the session protocol of AnyDesk before version 8.0.3. This allows unauthenticated remote attackers to execute arbitrary code, as demonstrated on Linux for command execution as root without victim approval for desktop control. The issue arises from a lack of validation for the payload length value. System administrators and security teams should assess exposure and prioritize patching to mitigate potential risks. Affected product deployments should be identified and owners assigned for follow-up.
Defensive priority
High priority for immediate patching or mitigation
Recommended defensive actions
- Immediately patch AnyDesk to version 8.0.3 or later
- Verify and limit exposure of AnyDesk installations
- Monitor for suspicious activity related to AnyDesk
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and source item provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish versions, exploitation, impact, or remediation beyond patching to version 8.0.3 or later.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-109390 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-109390
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-109390 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-109390
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
CVE-2026-109390
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/109xxx/CVE-2026-109390.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://github.com/v12-security/pocs/tree/main/anydesk
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://anydesk.com/en/changelog/linux
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.