dbcve.org
Digital Employee ExperienceApplication · Teamviewer

CVE-2025-64989

HIGH · 7.2 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 21.1 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 command injection vulnerability was discovered in TeamViewer DEX (former 1E DEX), specifically within the 1E-Explorer-TachyonCore-FindFileBySizeAndHash instruction prior V21.1. Improper input validation, allowing authenticated attackers with Actioner privileges to inject arbitrary commands. Exploitation enables remote execution of elevated commands on devices connected to the platform.

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 is a command injection vulnerability in TeamViewer DEX's TachyonCore component, specifically in the FindFileBySizeAndHash instruction prior to version 21.1. The vulnerability stems from improper input validation that allows authenticated attackers with Actioner privileges to inject arbitrary OS commands, which are then executed with elevated privileges on managed devices.

MitigationUpgrade to TachyonCore version 21.1 or later where the input validation has been properly implemented. Additionally, restrict Actioner privileges to only trusted users and monitor for suspicious command execution patterns.

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

CVSS:3.1/AV:N/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
    Locate TeamViewer DEX installation directories or check installed programs listing for TeamViewer Digital Employee Experience or Tachyon components
    Affected if TeamViewer DEX is installed and the version is below 21.1
  2. Check TachyonCore version
    Use system inventory or software enumeration tools to identify the installed version of TachyonCore or the parent DEX application; compare against the affected range (versions prior to 21.1)
    Affected if The installed TachyonCore or DEX version is lower than 21.1
  3. Verify FindFileBySizeAndHash instruction availability
    Check if the Tachyon instruction set includes the FindFileBySizeAndHash command; consult TachyonCore documentation or enumerate available instructions
    Affected if The FindFileBySizeAndHash instruction is present and accessible in the environment
  4. Review Actioner privilege assignments
    Examine user role configurations in the TeamViewer DEX administration console or user management settings to identify accounts granted Actioner privileges
    Affected if Any user account possesses Actioner privileges, particularly untrusted or external accounts

A system is affected if TeamViewer DEX with TachyonCore version below 21.1 is installed, the FindFileBySizeAndHash instruction is available, and users with Actioner privileges exist in the environment.

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

Upgrade to TachyonCore version 21.1 or later where the input validation has been properly implemented. Additionally, restrict Actioner privileges to only trusted users and monitor for suspicious command execution patterns.

Recommended fix High confidence

21.1

  1. Upgrade Digital Employee Experience (DEX) to version 21.1 or later to remediate the command injection vulnerability in the 1E-Explorer-TachyonCore-FindFileBySizeAndHash instruction

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

Fix this in Digital Employee Experience Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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