dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-2695

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 command injection vulnerability was discovered in TeamViewer DEX Platform On-Premises (former 1E DEX Platform On-Premises) prior to version 9.2. Improper input validation allows authenticated users with at least questioner privileges to inject commands in specific instructions. Exploitation could lead to execution of elevated commands on devices connected to the platform.

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 Platform On-Premises prior to version 9.2 due to improper input validation. Authenticated users with at least questioner privileges can inject commands into specific instructions, potentially executing elevated commands on devices connected to the platform.

MitigationUpgrade to TeamViewer DEX Platform On-Premises version 9.2 or later to obtain the patched version with proper input validation. Review user privilege assignments and limit questioner-level access until the upgrade is completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 Platform On-Premises installation
    Locate the TeamViewer DEX installation directory or check system services for 'TeamViewer DEX' or 'TV DEX' processes. Common paths may include C:\Program Files\TeamViewer\ or /opt/teamviewer/ on Linux systems.
    Affected if TeamViewer DEX Platform On-Premises is installed and running on the system.
  2. Determine installed version
    Check the installed version of TeamViewer DEX Platform On-Premises. This can typically be found in the application itself (Help > About), the installer metadata, or version files within the installation directory.
    Affected if The installed version is prior to 9.2 (e.g., 9.0, 9.1, or any version number less than 9.2).
  3. Verify questioner privilege users exist
    Access the TeamViewer DEX administration console and review user accounts. Look for users assigned the 'questioner' role or any role that includes questioner-level privileges.
    Affected if At least one user account has questioner privileges or higher access to the platform.
  4. Confirm accessible DEX instruction interface
    Check if the DEX instruction interface that accepts user input is enabled and accessible to questioner-level users. This may involve reviewing web application settings, API endpoints, or client configurations.
    Affected if The instruction input feature that accepts commands is enabled and reachable by authenticated questioner users.

The environment is affected if TeamViewer DEX Platform On-Premises version is below 9.2 AND at least one user with questioner privileges can access the instruction input feature.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to TeamViewer DEX Platform On-Premises version 9.2 or later to obtain the patched version with proper input validation. Review user privilege assignments and limit questioner-level access until the upgrade is completed.

Recommended fix Moderate confidence

TeamViewer DEX Platform On-Premises version 9.2

  1. 1. Identify the current version of TeamViewer DEX Platform On-Premises installation
  2. 2. Review the current version to confirm it is prior to version 9.2
  3. 3. Plan and schedule an upgrade to version 9.2 or later following TeamViewer's standard upgrade procedure
  4. 4. After upgrading, verify the installation is running version 9.2 or higher
  5. 5. Test that the command injection vulnerability is no longer present and the platform functions normally

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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