dbcve.org
Digital Employee ExperienceApplication · Teamviewer

CVE-2025-64991

HIGH · 7.2 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 15.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-PatchInsights-Deploy instruction prior V15. 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 · moderate confidence

A command injection vulnerability exists in TeamViewer DEX (formerly 1E DEX) within the 1E-PatchInsights-Deploy instruction prior to version 15. The vulnerability stems from improper input validation, allowing authenticated attackers with Actioner privileges to inject and execute arbitrary commands on devices connected to the platform with elevated privileges.

MitigationUpgrade to version 15 or later which implements proper input validation. Until then, restrict Actioner privileges to minimal required users and implement monitoring 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:< 15.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 version
    Locate the TeamViewer Digital Employee Experience (formerly 1E DEX) installation and check the installed version number. This is typically found in the software inventory, program files, or via the system's software management tools.
    Affected if The installed version is any version prior to 15.0 (e.g., 14.x, 13.x, etc.)
  2. Locate 1E-PatchInsights-Deploy instruction configuration
    Search the TeamViewer DEX configuration or instruction library for the presence and configuration of the 1E-PatchInsights-Deploy instruction. This may be found in the admin console, configuration files, or patch management settings.
    Affected if The 1E-PatchInsights-Deploy instruction exists and is enabled in the environment
  3. Identify accounts with Actioner privileges
    Review user roles and permissions within the TeamViewer DEX administration interface to enumerate accounts that hold Actioner privileges.
    Affected if Any user account possesses Actioner permissions, particularly those beyond the primary administrator
  4. Review command execution logs for PatchInsights-Deploy
    Examine logs, audit trails, or execution history within TeamViewer DEX for any instances where the 1E-PatchInsights-Deploy instruction was invoked. Look for unexpected or suspicious command patterns.
    Affected if There are execution records showing unusual or unexpected commands originating from the PatchInsights-Deploy instruction

You are affected if TeamViewer DEX version is below 15.0 AND the 1E-PatchInsights-Deploy instruction is enabled in your 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 15.0 or later
Fixed in 15.0
Interim mitigation

Upgrade to version 15 or later which implements proper input validation. Until then, restrict Actioner privileges to minimal required users and implement monitoring for suspicious command execution patterns.

Recommended fix Moderate confidence

Version 15.0 or later

  1. Verify current TeamViewer DEX (1E) installation version by checking the application or system information
  2. Confirm the installed version is below 15.0
  3. Plan and schedule an upgrade to version 15.0 or later during a maintenance window
  4. Download the version 15.0 or latest stable release from the official TeamViewer/1E download portal
  5. Review release notes for version 15.0 to understand changes and prerequisites
  6. Execute the upgrade following TeamViewer's standard upgrade procedure
  7. After upgrade, verify the 1E-PatchInsights-Deploy instruction is now at a version that includes the fix
  8. Test the patched functionality to confirm the input validation is properly enforced
Caveat Review version 15.0 release notes for any configuration or feature changes that may affect existing workflows; test in non-production environment first

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

Fix this in Digital Employee Experience Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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