Digital Employee ExperienceApplication · Teamviewer

CVE-2026-23569

HIGH · 7.5 CVSS v3.1 Published 2026-01-29
Fix available
A fix is available. Upgrade to 26.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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 a remote attacker to leak stack memory and cause a denial of service via a crafted request. The leaked stack memory could be used to bypass ASLR remotely and facilitate exploitation of other vulnerabilities on the affected system.

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

Out-of-bounds read vulnerability in the TeamViewer DEX Client (formerly 1E Client) Content Distribution Service (NomadBranch.exe) allows remote attackers to leak stack memory via crafted requests, potentially bypassing ASLR and facilitating further exploitation. The vulnerability affects versions prior to 26.1 for Windows.

MitigationUpdate TeamViewer DEX Client to version 26.1 or later to patch the out-of-bounds read 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:< 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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 TeamViewer DEX Client installation
    Search for NomadBranch.exe in typical installation paths such as C:\Program Files\1E\Client\ or C:\Program Files\TeamViewer\Digital Employee Experience\, or use Get-Process to check if NomadBranch.exe is running
    Affected if NomadBranch.exe is present on the system
  2. Determine installed version of NomadBranch.exe
    Right-click NomadBranch.exe, select Properties, and view the File Version field, or run (Get-Item 'C:\Program Files\1E\Client\NomadBranch.exe').VersionInfo to retrieve version programmatically
    Affected if Version displays as a number lower than 26.1 (for example 26.0, 25.x, or any earlier version)
  3. Verify Content Distribution Service status
    Open Services.msc and locate the 1E Client Content Distribution service, or run Get-Service -Name '1E Client Content Distribution' to confirm it is running
    Affected if The Content Distribution Service (NomadBranch.exe) is installed and actively running

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

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

Update TeamViewer DEX Client to version 26.1 or later to patch the out-of-bounds read vulnerability.

Recommended fix Moderate confidence

TeamViewer DEX Client version 26.1 for Windows

  1. Navigate to the official TeamViewer download page at www.teamviewer.com
  2. Locate and download the Digital Employee Experience (DEX) Client version 26.1 or later for Windows
  3. Verify the downloaded installer is version 26.1 or higher before proceeding
  4. Stop the Content Distribution Service (NomadBranch.exe) if currently running
  5. Run the installer and follow the on-screen prompts to upgrade the TeamViewer DEX Client
  6. Confirm the installation completed successfully by checking the version in the application
  7. Restart the Content Distribution Service (NomadBranch.exe)

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