dbcve.org
Digital Employee ExperienceApplication · Teamviewer

CVE-2025-64995

MEDIUM · 6.7 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 3.4 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-Exchange-NomadClientHealth-ConfigureGeneralSetting instruction prior V3.4. Improper protection of the execution path on the local device allows attackers, with local access to the device during execution, to hijack the process and execute arbitrary code with SYSTEM privileges.

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

A local privilege escalation vulnerability exists in TeamViewer DEX (formerly 1E DEX) in the 1E-Exchange-NomadClientHealth-ConfigureGeneralSetting instruction for versions prior to V3.4. The instruction lacks proper protection of its execution path on the local device, allowing an attacker with local access to hijack the process and execute arbitrary code with SYSTEM-level privileges.

MitigationUpgrade TeamViewer DEX to version 3.4 or later to address the improper execution path protection. Additionally, ensure strict physical access controls and limit local administrator privileges to reduce the attack surface.

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:< 3.4

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
    Look for TeamViewer DEX or 1E DEX installation directory, typically under Program Files or Program Files (x86). Check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'TeamViewer DEX' or '1E DEX'.
    Affected if TeamViewer DEX is installed and version is below 3.4.0
  2. Determine installed version number
    Right-click the TeamViewer DEX executable (typically DEX.exe or similar) in the installation folder, select Properties, then check the Details tab for the File Version. Alternatively, query the registry key found in the uninstall entry for the DisplayVersion value.
    Affected if Version displayed is less than 3.4 (e.g., 3.3.x, 3.2.x, etc.)
  3. Verify the vulnerable instruction exists
    Examine the TeamViewer DEX configuration or instruction library for the presence of '1E-Exchange-NomadClientHealth-ConfigureGeneralSetting' instruction. This may be found in the installation folder under a Config, Instructions, or Templates subdirectory, or within the application database/configuration file.
    Affected if The 1E-Exchange-NomadClientHealth-ConfigureGeneralSetting instruction is present in the installation, indicating the vulnerable component is available.

A system is affected if TeamViewer DEX (formerly 1E DEX) is installed with a version number lower than 3.4, as versions prior to V3.4 contain the improperly protected execution path in the specified instruction.

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

Upgrade TeamViewer DEX to version 3.4 or later to address the improper execution path protection. Additionally, ensure strict physical access controls and limit local administrator privileges to reduce the attack surface.

Recommended fix High confidence

3.4

  1. 1. Back up all existing TeamViewer DEX configuration, policies, and any associated data before starting the upgrade process.
  2. 2. Obtain the TeamViewer DEX version 3.4 (or later) installer from the official TeamViewer download portal or your licensed distribution channel.
  3. 3. Consult the official TeamViewer DEX upgrade documentation for version 3.4 to ensure all prerequisites are met.
  4. 4. Execute the version 3.4 installer on the affected system, following the documented installation or upgrade procedure.
  5. 5. After installation, verify that the 1E-Exchange-NomadClientHealth-ConfigureGeneralSetting instruction is running the fixed version.
  6. 6. Confirm the installed version displays as 3.4 or later and validate that SYSTEM-level processes are no longer vulnerable to DLL hijacking.
Caveat Review release notes for any configuration or behavioral changes between your current version and 3.4

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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