dbcve.org
Digital Employee ExperienceApplication · Teamviewer

CVE-2026-23570

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-29
Fix available
A fix is available. Upgrade to 26.1 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 missing validation of a user-controlled value in the TeamViewer DEX Client (former 1E Client) - Content Distribution Service (NomadBranch.exe) prior version 26.1 for Windows allows an adjacent network attacker to tamper with log timestamps via crafted UDP Sync command. This could result in forged or nonsensical datetime prefixes and compromising log integrity and forensic correlation.

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

A missing validation of user-controlled value in the TeamViewer DEX Client (formerly 1E Client) Content Distribution Service (NomadBranch.exe) prior to version 26.1 allows an adjacent network attacker to send crafted UDP Sync commands that tamper with log timestamps, resulting in forged or nonsensical datetime prefixes that compromise log integrity and forensic correlation.

MitigationUpgrade the TeamViewer DEX Client (1E Client) to version 26.1 or later. As a compensating control, restrict network access to the UDP port used by the Content Distribution Service to trusted adjacent network segments only.

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Check if TeamViewer DEX Client or 1E Client is installed
    Look for NomadBranch.exe in the installation directory (commonly in Program Files\1E or Program Files\TeamViewer) or check Add/Remove Programs for TeamViewer DEX or 1E Client entries
    Affected if The software is present on the system
  2. Determine the installed version of NomadBranch.exe
    Right-click NomadBranch.exe, select Properties, and check the File Version in the Details tab. Alternatively, run 'wmic product where "name like '%1E%' or name like '%TeamViewer DEX%' get version' or use Get-Item on the executable
    Affected if The version is lower than 26.1
  3. Verify the Content Distribution Service is running
    Open Services console (services.msc) and look for '1E Client' or 'TeamViewer DEX Content Distribution' service, or run 'Get-Service | Where-Object {$_.DisplayName -match "1E|Content Distribution"}'
    Affected if The service is running and the version is below 26.1
  4. Confirm UDP listener is active on the Content Distribution Service
    Run 'netstat -an | findstr "UDP"' and look for UDP ports associated with NomadBranch.exe, or use 'Get-NetUDPEndpoint | Where-Object {$_.OwningProcess -match (Get-Process NomadBranch).Id}'
    Affected if A UDP listener is bound and the version is below 26.1

A user is affected if the TeamViewer DEX Client (1E Client) with NomadBranch.exe version below 26.1 is installed and the Content Distribution Service UDP listener is active, allowing adjacent network attackers to send crafted packets.

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. As a compensating control, restrict network access to the UDP port used by the Content Distribution Service to trusted adjacent network segments only.

Recommended fix Moderate confidence

TeamViewer DEX Client version 26.1 or later

  1. Identify systems running the TeamViewer DEX Client (formerly 1E Client) with NomadBranch.exe on Windows
  2. Check the current version of the Digital Employee Experience client (look for versions prior to 26.1)
  3. Obtain version 26.1 or later of the TeamViewer DEX Client from the official vendor
  4. Upgrade the Digital Employee Experience client to version 26.1 or later on all affected Windows systems
  5. Verify the upgrade was successful by checking the NomadBranch.exe version and confirming UDP Sync commands are properly validating timestamps

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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