dbcve.org
Digital Employee ExperienceApplication · Teamviewer

CVE-2025-64994

MEDIUM · 6.7 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 17.1 or later.
See remediation →
69/100
Remediation priority · Elevated
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
A privilege escalation vulnerability was discovered in TeamViewer DEX (former 1E DEX), specifically within the 1E-Nomad-SetWorkRate instruction prior V17.1. The improper handling of executable search paths could allow local attackers with write access to a PATH directory on a device to escalate privileges and execute arbitrary code as SYSTEM.

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 · moderate confidence

The 1E-Nomad-SetWorkRate instruction in TeamViewer DEX versions prior to V17.1 improperly handles executable search paths, allowing a local attacker with write access to any directory in the system PATH to place a malicious executable that will be invoked with SYSTEM privileges when the vulnerable instruction executes.

MitigationUpgrade TeamViewer DEX to version V17.1 or later to remediate this vulnerability.

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
Digital Employee ExperienceApplication
Affected:< 17.1

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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. Identify TeamViewer DEX installation and version
    Check the installed version of TeamViewer Digital Employee Experience. This can typically be found in Add/Remove Programs, the software's About/Help section, or by querying the installed programs list via system tools.
    Affected if The installed version is prior to V17.1 (e.g., V17.0, V16.x, or earlier)
  2. Confirm the 1E-Nomad-SetWorkRate instruction is present
    Verify that the TeamViewer DEX installation includes the 1E-Nomad-SetWorkRate instruction module. This is typically part of the Nomad component within the DEX platform.
    Affected if The 1E-Nomad-SetWorkRate instruction module is present in the installation
  3. Check if Nomad feature is enabled
    Determine whether the Nomad feature within TeamViewer DEX is enabled and actively used in the environment. This can be verified through the DEX configuration settings or administrative console.
    Affected if The Nomad feature is enabled and the SetWorkRate instruction can be triggered
  4. Identify writable directories in system PATH
    Review the system PATH environment variable and identify any directories that are writable by non-privileged users. Use system tools or commands to enumerate PATH directories and check write permissions.
    Affected if Any directory in the system PATH is writable by a local attacker

A user is affected if TeamViewer DEX version is below V17.1, the 1E-Nomad-SetWorkRate instruction is present and enabled, and writable directories exist in the system PATH that could allow PATH injection.

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 17.1 or later
Fixed in 17.1
Interim mitigation

Upgrade TeamViewer DEX to version V17.1 or later to remediate this vulnerability.

Recommended fix Moderate confidence

17.1

  1. Identify the current installed version of TeamViewer DEX (Digital Employee Experience)
  2. Download TeamViewer DEX version 17.1 from the official TeamViewer website or your licensed distribution channel
  3. Create a backup of the current configuration if applicable
  4. Run the installer for version 17.1 with appropriate administrative privileges
  5. Follow the installation wizard to complete the upgrade
  6. Verify the installation completed successfully
  7. Confirm the installed version is 17.1 or higher

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

Fix this in Digital Employee Experience Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64994 — 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-64994 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