CVE-2025-64990
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 command injection vulnerability was discovered in TeamViewer DEX (former 1E DEX), specifically within the 1E-Explorer-TachyonCore-LogoffUser instruction prior V21.1. Improper input validation, allowing authenticated attackers with Actioner privileges to inject arbitrary commands. Exploitation enables remote 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 confidenceA command injection vulnerability exists in TeamViewer DEX (formerly 1E DEX) within the 1E-Explorer-TachyonCore-LogoffUser instruction for versions prior to V21.1. The vulnerability stems from improper input validation, allowing authenticated attackers with Actioner privileges to inject and execute arbitrary commands with elevated privileges on devices connected to the platform.
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< 21.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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed TeamViewer DEX versionLocate the TeamViewer DEX installation directory and check the version information, typically found in the application metadata, installer log, or program information panelAffected if The installed version is below 21.1 (any version prior to V21.1)
-
Confirm TachyonCore module is presentVerify the 1E-Explorer-TachyonCore component is installed as part of the TeamViewer DEX deploymentAffected if TachyonCore module exists and the version is less than 21.1
-
Check LogoffUser instruction availabilityExamine the available Tachyon instructions within the platform, specifically looking for the LogoffUser instruction in the instruction setAffected if The LogoffUser instruction is present in the Tachyon instruction catalog
-
Verify Actioner privilege configurationReview user role assignments in the TeamViewer DEX administration console to identify accounts granted Actioner privilegesAffected if Any user accounts possess Actioner privileges, creating the attacker vector for this vulnerability
-
Audit for suspicious command executionReview platform audit logs and command execution history for any anomalous or unauthorized commands that may have been run through the LogoffUser instructionAffected if Unexplained or unauthorized command executions appear in logs, especially those originating from Actioner users
Your environment is affected if TeamViewer DEX with TachyonCore is installed at a version prior to 21.1 and the LogoffUser instruction is accessible to users with Actioner privileges.
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 · scoped21.1
Upgrade to TeamViewer DEX version 21.1 or later to obtain the patched LogoffUser instruction. Additionally, limit Actioner privileges to only necessary personnel and monitor for suspicious command execution patterns.
21.1
- Upgrade TeamViewer DEX (1E DEX) to version 21.1 or later
- After upgrading, verify the 1E-Explorer-TachyonCore-LogoffUser instruction is no longer vulnerable to command injection
- Confirm authenticated users with Actioner privileges can no longer inject arbitrary commands through the LogoffUser instruction
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64990 — 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-2025-64990 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