CVE-2026-23565
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 · uneditedA vulnerability in 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 the NomadBranch.exe process to terminate via crafted requests. This can result in a denial-of-service condition of the Content Distribution Service.
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 confidenceThis is a denial-of-service vulnerability in TeamViewer DEX Client's Content Distribution Service (NomadBranch.exe). An attacker positioned on the adjacent network can send specially crafted requests to the NomadBranch.exe process, causing it to terminate unexpectedly and disrupt the Content Distribution Service.
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< 26.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify TeamViewer DEX Client installationCheck for presence of TeamViewer DEX (1E Client) installation by looking for NomadBranch.exe in Program Files directories, or check Windows Services for TeamViewer DEX-related services using 'Get-Service | Where-Object {$_.DisplayName -like "*TeamViewer*" -or $_.DisplayName -like "*1E*"}'Affected if TeamViewer DEX Client (1E Client) is installed on the system
-
Check installed version against affected rangeQuery the version of the installed TeamViewer DEX Client (1E Client). In PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like "*TeamViewer*" -or $_.DisplayName -like "*1E*"} | Select-Object DisplayName, DisplayVersion. Alternatively, right-click NomadBranch.exe in the installation folder and view Properties > Details for version information.Affected if The installed version is lower than 26.1
-
Confirm NomadBranch.exe process is runningOpen Task Manager or run 'Get-Process NomadBranch' in PowerShell to check if the Content Distribution Service process is currently activeAffected if NomadBranch.exe process is running on the system
-
Assess network exposureDetermine if the system is on a network segment where adjacent attackers could send requests to the NomadBranch.exe service. Check network adapter settings and verify if the system is on a trusted internal network versus a shared/public network.Affected if The system is on an exposed network segment where untrusted adjacent devices can communicate with the host
A system is affected if TeamViewer DEX Client (1E Client) version lower than 26.1 is installed with the NomadBranch.exe process running on an accessible network segment.
Generated from the published advisory. Verify against your own configuration.
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 · scoped26.1
Upgrade TeamViewer DEX Client (1E Client) to version 26.1 or later to remediate this vulnerability.
26.1
- Identify the current version of TeamViewer DEX Client (1E Client) installed by checking the NomadBranch.exe file version or using system inventory tools
- Download TeamViewer DEX Client version 26.1 or later from the official TeamViewer website or vendor distribution channel
- Review TeamViewer DEX upgrade documentation for any prerequisites or migration considerations
- Apply the upgrade to the TeamViewer DEX Client following standard deployment procedures
- Verify the upgrade was successful by confirming the NomadBranch.exe version is 26.1 or later
- Test that the Content Distribution Service (NomadBranch.exe) is running normally after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23565 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-23565 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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