Digital Employee ExperienceApplication · Teamviewer

CVE-2025-12687

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 25.11 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges 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 vulnerability in TeamViewer DEX Client (former 1E Client) - Content Distribution Service (NomadBranch.exe) prior version 25.11 for Windows allows malicious actors to cause a denial of service (application crash) via a crafted command, resulting in service termination.

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 denial of service vulnerability exists in the TeamViewer DEX Client (formerly 1E Client) Content Distribution Service (NomadBranch.exe) on Windows. The vulnerability allows remote attackers to send a crafted command to the service prior to version 25.11, causing the application to crash and terminate unexpectedly.

MitigationUpdate TeamViewer DEX Client (1E Client) to version 25.11 or later to resolve this vulnerability. Organizations should verify all deployed instances are running the patched version.

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

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Locate the NomadBranch.exe service
    Open Services (services.msc) and search for Content Distribution Service, or run 'tasklist /FI "IMAGENAME eq NomadBranch.exe"' in Command Prompt
    Affected if The NomadBranch.exe process or service is found - indicating TeamViewer DEX Client (1E Client) is installed
  2. Identify installed version of TeamViewer DEX Client
    Open Programs and Features (appwiz.cpl) and locate TeamViewer Digital Employee Experience or 1E Client entry to view version, or right-click the NomadBranch.exe file in the installation directory and check Properties > Details for File Version
    Affected if Cannot locate the product or the version is not visible
  3. Compare version against affected range
    Review the installed version number - look for major.minor.build format (e.g., 25.10, 25.6, 24.5)
    Affected if Installed version is less than 25.11 (for example: 25.10, 25.6, 24.x, any earlier version)

Your environment is affected if NomadBranch.exe is present and the installed version of TeamViewer DEX Client (1E Client) is below 25.11.

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

Update TeamViewer DEX Client (1E Client) to version 25.11 or later to resolve this vulnerability. Organizations should verify all deployed instances are running the patched version.

Recommended fix High confidence

25.11

  1. 1. Identify all systems running TeamViewer DEX Client (formerly 1E Client) on Windows
  2. 2. Verify current version by checking NomadBranch.exe file version or checking the installed version through Programs and Features
  3. 3. Download the updated TeamViewer DEX Client version 25.11 from the official TeamViewer website or your licensed download portal
  4. 4. Deploy the update following your organization's change management procedures
  5. 5. Verify successful installation by confirming version 25.11 is installed on affected systems
  6. 6. Test that the Content Distribution Service (NomadBranch.exe) runs normally after update

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-12687 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-12687 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