dbcve.org
Digital Employee ExperienceApplication · Teamviewer

CVE-2025-46266

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 coerce the service into transmitting data to an arbitrary internal IP address, potentially leaking sensitive information.

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

The TeamViewer DEX Client's Content Distribution Service (NomadBranch.exe) prior to version 25.11 for Windows contains a vulnerability allowing an attacker to coerce the service into transmitting data to an arbitrary internal IP address. This SSRF-like flaw enables potential exfiltration of sensitive data to attacker-controlled internal destinations.

MitigationUpgrade TeamViewer DEX Client (1E Client) to version 25.11 or later to remediate this vulnerability.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Verify TeamViewer DEX Client installation
    Check for the presence of TeamViewer DEX Client (also known as 1E Client) on the Windows system. Look in Program Files or Program Files (x86) for a 'TeamViewer' or '1E' folder, or check the list of installed programs in Control Panel > Programs and Features.
    Affected if The TeamViewer DEX Client (1E Client) is installed on the system
  2. Determine installed version
    Locate the version information for the TeamViewer DEX Client. Check the file properties of NomadBranch.exe (typically found in the TeamViewer/1E Client installation directory), or query the installed programs registry key for the version. Compare the version number to 25.11.
    Affected if The installed version is lower than 25.11 (e.g., 25.10, 25.9, etc.)
  3. Confirm NomadBranch.exe presence
    Verify that NomadBranch.exe (Content Distribution Service) exists in the TeamViewer DEX Client installation directory and is currently running as a service or process. Use Task Manager or command 'tasklist /FI "IMAGENAME eq NomadBranch.exe"' to check if the process is active.
    Affected if NomadBranch.exe is present and running on the system
  4. Inspect Content Distribution Service configuration
    Examine the configuration files or registry settings associated with the Content Distribution Service (NomadBranch.exe) for any suspicious or unexpected internal IP address destinations configured for data transmission.
    Affected if The service configuration shows connections to unexpected or arbitrary internal IP addresses

The system is affected if TeamViewer DEX Client version is below 25.11 AND the NomadBranch.exe Content Distribution Service is running.

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

Upgrade TeamViewer DEX Client (1E Client) to version 25.11 or later to remediate this vulnerability.

Recommended fix Moderate confidence

25.11

  1. Obtain the TeamViewer DEX Client version 25.11 or later from the official TeamViewer website or your organization's software distribution channel
  2. Verify the digital signature and integrity of the downloaded installer before execution
  3. Plan the upgrade during a maintenance window to minimize disruption
  4. Backup any critical configuration settings if applicable
  5. Deploy the upgrade to affected Windows systems running the Content Distribution Service (NomadBranch.exe)
  6. Verify the upgrade was successful by checking the version of NomadBranch.exe shows 25.11 or later
  7. Confirm the Content Distribution Service is running normally after the upgrade

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-46266 — 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-46266 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