# CVE-2026-2695: Lack of Server-side validation in Instruction Input in TeamViewer DEX Platform (On-Premises)

> Authenticated users can inject commands to execute elevated code on connected devices via improper input validation in the TeamViewer DEX Platform.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-567r-vw5w-g2q6

## What is CVE-2026-2695?

CVE-2026-2695 is a medium-severity command injection vulnerability in TeamViewer DEX (On-Premises), published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-2695?


## How do I fix CVE-2026-2695?

No fix has been published for CVE-2026-2695 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2695 being exploited?

There is no known exploitation of CVE-2026-2695 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2695 and fix it if it is affected.

What it is: CVE-2026-2695 is a medium-severity command injection vulnerability in TeamViewer DEX (On-Premises), published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2695 in the wild and no public exploit code.

Affected product: TeamViewer DEX (On-Premises). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2695/ (Markdown: https://insights.sbomify.com/CVE-2026-2695/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2695
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2695
- OSV: https://osv.dev/vulnerability/CVE-2026-2695

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2695/
Summaries are generated and may contain mistakes; the official description above is the record.
