dbcve.org
Digital Employee ExperienceApplication · Teamviewer

CVE-2026-23568

HIGH · 8.1 CVSS v3.1 Published 2026-01-29
Fix available
A fix is available. Upgrade to 26.1 or later.
See remediation →
86/100
Remediation priority · High
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
An out-of-bounds read vulnerability in the TeamViewer DEX Client (former 1E Client) - Content Distribution Service (NomadBranch.exe) prior version 26.1 for Windows allows an attacker on the adjacent network to cause information disclosure or denial-of-service via a special crafted packet. The leaked memory could be used to bypass ASLR and facilitate further exploitation.

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

An out-of-bounds read vulnerability exists in the TeamViewer DEX Client (1E Client) Content Distribution Service (NomadBranch.exe) prior to version 26.1 for Windows. An attacker on the adjacent network can send a specially crafted packet to trigger the vulnerability, leading to information disclosure or denial-of-service. The memory leakage can be leveraged to bypass ASLR and enable further exploitation.

MitigationUpgrade the TeamViewer DEX Client / 1E Client to version 26.1 or later to address the vulnerability. Until patched, consider network segmentation to limit adjacent network attack surface.

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/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. Check if TeamViewer DEX / 1E Client is installed
    Open Windows Settings > Apps & Features (or run 'appwiz.cpl') and search for 'TeamViewer DEX' or '1E Client' or 'TeamViewer Digital Employee Experience'. Alternatively, check Program Files for a TeamViewer or 1E folder.
    Affected if The application is not listed or the version cannot be determined, proceed to check the service directly.
  2. Identify the NomadBranch.exe service
    Open Task Manager or Services.msc and look for a process or service named 'NomadBranch' or 'TeamViewer DEX Content Distribution Service'. You can also run 'tasklist /FI "IMAGENAME eq NomadBranch.exe"' or check Services under the 'TeamViewer DEX' or '1E' namespace.
    Affected if The NomadBranch.exe process or service is not running or does not exist, the vulnerability is not currently exploitable in your environment.
  3. Determine the installed version of the affected component
    Right-click on NomadBranch.exe in Task Manager, select 'Properties', and check the 'Details' tab for version information. Alternatively, navigate to the installation directory (typically C:\Program Files\TeamViewer\ or C:\Program Files\1E\), locate NomadBranch.exe, right-click and view Properties > Details for the File Version.
    Affected if The version shown is lower than 26.1 (for example, 25.x, 24.x, etc.) or if the version field is blank/unavailable, your environment may be affected.
  4. Verify product version in registry or application
    Run the TeamViewer DEX / 1E Client application if installed and navigate to Help > About to view the version number. Alternatively, check the Windows Registry under HKLM\SOFTWARE\TeamViewer or HKLM\SOFTWARE\1E for a Version entry.
    Affected if The version displayed is below 26.1, indicating the installed build is vulnerable to CVE-2026-23568.

Your environment is affected if TeamViewer DEX / 1E Client with NomadBranch.exe is installed with a version lower than 26.1 and the Content Distribution Service is active.

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

Upgrade the TeamViewer DEX Client / 1E Client to version 26.1 or later to address the vulnerability. Until patched, consider network segmentation to limit adjacent network attack surface.

Recommended fix High confidence

Version 26.1

  1. 1. Identify systems running TeamViewer DEX Client (formerly 1E Client) or Content Distribution Service (NomadBranch.exe) on Windows
  2. 2. Check the current version of the installed software (NomadBranch.exe)
  3. 3. Obtain the updated version 26.1 or later from the official TeamViewer website or vendor distribution channels
  4. 4. Deploy and apply the update to all affected systems following standard patch management procedures
  5. 5. Verify the update was successfully applied by confirming the version is 26.1 or higher

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-2026-23568 — 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-2026-23568 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