dbcve.org
Digital Employee ExperienceApplication · Teamviewer

CVE-2025-64987

HIGH · 7.2 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 21.0 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-CheckSimpleIoC instruction. 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

A command injection vulnerability exists in TeamViewer DEX (1E DEX) within the 1E-Explorer-TachyonCore-CheckSimpleIoC instruction due to improper input validation. Authenticated attackers with Actioner privileges can inject arbitrary commands through this instruction, achieving remote execution of elevated commands on devices connected to the platform.

MitigationImplement strict input validation and sanitization on the CheckSimpleIoC instruction to prevent command injection. Use parameterized queries or allowlists for any command execution paths, and restrict Actioner privilege assignments until a patch is applied.

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.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
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
    Check for TeamViewer Digital Employee Experience (1E DEX) or Tachyon Core components in installed programs, or look for the Tachyon Explorer service running on the system
    Affected if TeamViewer DEX or 1E Tachyon Core is installed on the system
  2. Determine installed version
    Open the TeamViewer DEX / 1E Explorer application, or check the installed programs list for the exact version number
    Affected if The installed version is lower than 21.0 (versions like 20.x, 19.x, etc.)
  3. Check Tachyon Core components
    Verify if the 1E-Explorer-TachyonCore component is present by examining installed software or the Tachyon Explorer interface
    Affected if TachyonCore components are installed and active
  4. Review Actioner privilege assignments
    Access the TeamViewer DEX / Tachyon administration console and examine user or group role assignments, specifically looking for the Actioner role
    Affected if Any user account or group is assigned Actioner privileges in the platform
  5. Verify CheckSimpleIoC instruction availability
    In the Tachyon Explorer interface, check if the CheckSimpleIoC instruction is listed as an available instruction that can be executed
    Affected if The CheckSimpleIoC instruction is accessible and enabled in the instruction set

The environment is affected if TeamViewer DEX (1E Tachyon) is installed with a version lower than 21.0 and the CheckSimpleIoC instruction is available to users with Actioner privileges.

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.0 or later
Fixed in 21.0
Interim mitigation

Implement strict input validation and sanitization on the CheckSimpleIoC instruction to prevent command injection. Use parameterized queries or allowlists for any command execution paths, and restrict Actioner privilege assignments until a patch is applied.

Recommended fix High confidence

21.0

  1. Back up the current TeamViewer DEX installation and any associated configuration data
  2. Download TeamViewer Digital Employee Experience version 21.0 or later from the official TeamViewer website or vendor distribution channel
  3. Review the official upgrade documentation for TeamViewer DEX 21.0 to understand any specific migration requirements
  4. Install or upgrade to version 21.0 following the vendor's documented upgrade procedure
  5. After upgrade, verify the 1E-Explorer-TachyonCore-CheckSimpleIoC instruction is functioning correctly and that the fix is applied
  6. Confirm that authenticated users with Actioner privileges can no longer inject arbitrary commands through this vector
Caveat Review release notes for any configuration or behavioral changes in version 21.0

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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