dbcve.org
Digital Employee ExperienceApplication · Teamviewer

CVE-2026-23571

MEDIUM · 6.8 CVSS v3.1 Published 2026-01-29
Fix available
A fix is available. Upgrade to 26.1 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable

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 command injection vulnerability was discovered in TeamViewer DEX (former 1E DEX), specifically within the 1E-Nomad-RunPkgStatusRequest instruction. Improper input validation allows authenticated attackers with actioner privilege to run elevated arbitrary commands on connected hosts via malicious commands injected into the instruction’s input field. Users of 1E Client version 24.5 or higher are not affected.

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 command injection vulnerability exists in TeamViewer DEX (formerly 1E DEX) within the 1E-Nomad-RunPkgStatusRequest instruction. The vulnerability stems from improper input validation that allows authenticated attackers with actioner privilege to inject and execute arbitrary commands with elevated privileges on connected hosts through the instruction's input field.

MitigationUpgrade 1E Client to version 24.5 or higher to remediate this vulnerability. Until patched, limit actioner privilege to trusted personnel only and monitor for suspicious command execution.

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
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/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. Identify TeamViewer DEX installation
    Locate the 1E Client installation on the system. Check for presence of TeamViewer DEX or 1E DEX software by querying installed programs (Windows: Registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or use 'Get-ItemProperty' PowerShell command), or look for 1E client executables in Program Files directory
    Affected if TeamViewer DEX or 1E Client is not found on the system, then not affected
  2. Determine installed version
    Query the installed version of the 1E Client/TeamViewer DEX. Common locations: check file version of the main executable (typically in C:\Program Files\1E\Client\ or via PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\1E' -ErrorAction SilentlyContinue | Select-Object ClientVersion)
    Affected if Installed version is less than 26.1 (e.g., 26.0, 25.x, 24.x) - this indicates the version falls within the vulnerable range
  3. Verify 1E-Nomad module availability
    Confirm whether the 1E-Nomad module is loaded and active. This is typically configured in the 1E Client configuration files (e.g., Tachyon.config or NomadAgent.config) or can be queried via the 1E instruction 'GetInstructionDefinitions' if you have access
    Affected if 1E-Nomad-RunPkgStatusRequest instruction is present and enabled in the deployment
  4. Review actioner privilege assignments
    Examine the 1E Client role-based access control configuration to determine which users or groups have actioner privileges. Check the Authorization database, Tachyon Switch or 1E Platform admin console for role definitions containing actioner permissions
    Affected if Untrusted or unknown users have been granted actioner privileges, enabling them to issue the vulnerable instruction

The environment is affected if TeamViewer DEX/1E Client version is below 26.1 AND the 1E-Nomad module is active AND untrusted users possess actioner privilege to execute the 1E-Nomad-RunPkgStatusRequest instruction.

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 1E Client to version 24.5 or higher to remediate this vulnerability. Until patched, limit actioner privilege to trusted personnel only and monitor for suspicious command execution.

Recommended fix High confidence

TeamViewer DEX version 26.1 or later (latest stable release)

  1. Confirm current TeamViewer DEX (1E DEX) version by checking the 1E Client or DEX installation
  2. If running version < 26.1, identify the appropriate upgrade path for your deployment
  3. Upgrade to TeamViewer DEX version 26.1 or later (or the latest stable release)
  4. Alternatively, ensure all 1E Client installations are upgraded to version 24.5 or higher, as this also mitigates the vulnerability
  5. After upgrade, verify the 1E-Nomad-RunPkgStatusRequest instruction no longer accepts malicious command injection
  6. Confirm normal functionality of Nomad package status requests continues to work as expected
Caveat Review release notes for 26.x for any configuration or behavioral changes that may affect existing deployments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Employee Experience Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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