dbcve.org
AnydeskApplication

CVE-2025-27918

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-06
Fix available
A fix is available. Upgrade to 9.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in AnyDesk for Windows before 9.0.5, AnyDesk for macOS before 9.0.1, AnyDesk for Linux before 7.0.0, AnyDesk for iOS before 7.1.2, and AnyDesk for Android before 8.0.0. It has an integer overflow and resultant heap-based buffer overflow via a UDP packet during processing of an Identity user image within the Discovery feature, or when establishing a connection between any two clients.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This vulnerability involves an integer overflow in AnyDesk's UDP packet processing that leads to a heap-based buffer overflow. The flaw occurs when processing Identity user images within the Discovery feature or during client-to-client connection establishment, allowing remote code execution via specially crafted UDP packets.

MitigationUpdate AnyDesk to version 9.0.5 or later on Windows, 9.0.1 or later on macOS, 7.0.0 or later on Linux, 7.1.2 or later on iOS, and 8.0.0 or later on Android. If immediate patching is not possible, consider disabling the Discovery feature and restricting UDP-based connections through network segmentation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AnydeskApplication
Affected:< 9.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed AnyDesk version
    On Windows, open Programs and Features or run 'ad -v' in AnyDesk folder. On macOS, check /Applications/AnyDesk.app info. On Linux, run 'anydesk --version' or check package manager. On mobile, check app store or device settings.
    Affected if Version is below 9.0.0 on any platform (Windows, macOS, Linux, iOS, Android)
  2. Verify Discovery feature status
    Open AnyDesk settings, navigate to Privacy or Network settings, look for 'Discovery' or 'LAN Discovery' option. On Windows, this may be in the advanced settings or registry key.
    Affected if Discovery feature is enabled and version is below 9.0.0, allowing remote exploitation via LAN UDP packets
  3. Confirm UDP listener is active
    Run 'netstat -anp | grep anydesk' or 'ss -ulnp | grep anydesk' on Linux. On Windows, use 'netstat -an' and look for UDP listeners on AnyDesk ports (typically 7070, 50001-50010). Check if anydesk.exe is bound to UDP addresses.
    Affected if AnyDesk is listening on UDP ports and version is below 9.0.0, making the vulnerable UDP packet processing code active

User is affected if AnyDesk version is below 9.0.0 AND the Discovery feature is enabled OR UDP connections are accepted, allowing remote code execution via specially crafted UDP packets to the Discovery or client-to-client connection handlers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.0 or later
Fixed in 9.0.0
Interim mitigation

Update AnyDesk to version 9.0.5 or later on Windows, 9.0.1 or later on macOS, 7.0.0 or later on Linux, 7.1.2 or later on iOS, and 8.0.0 or later on Android. If immediate patching is not possible, consider disabling the Discovery feature and restricting UDP-based connections through network segmentation.

Recommended fix High confidence

Windows: 9.0.5+, macOS: 9.0.1+, Linux: 7.0.0+, iOS: 7.1.2+, Android: 8.0.0+

  1. Identify the platform(s) where AnyDesk is installed (Windows, macOS, Linux, iOS, or Android)
  2. For Windows: Navigate to anydesk.com or the official download page and download AnyDesk version 9.0.5 or later
  3. For macOS: Navigate to anydesk.com or the official download page and download AnyDesk version 9.0.1 or later
  4. For Linux: Navigate to anydesk.com or the official download page and download AnyDesk version 7.0.0 or later
  5. For iOS: Open the App Store, search for AnyDesk, and update to version 7.1.2 or later
  6. For Android: Open Google Play Store, search for AnyDesk, and update to version 8.0.0 or later
  7. Uninstall any older versions of AnyDesk from all affected systems
  8. Install the downloaded updated version of AnyDesk
Caveat Review AnyDesk release notes for your specific platform for any feature changes or configuration requirements between your current version and the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Anydesk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27918 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27918 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data