CyberSecBulletin
CVE-2026-19743NVD status: Deferred

Full Client: Improper Limitation of a Pathname to a Restricted Directory

Published Updated By the CyberSecBulletin desk

CVE-2026-19743 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in Full Client from TeamViewer, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 15.82, 15.64.8 (Legacy Windows 7 & 8), 14.7.48855 (Windows) as the first without the flaw, so updating Full Client to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.15% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Full Client to 15.82 or 15.64.8 (Legacy Windows 7 & 8) or 14.7.48855 (Windows) or 13.2.36230 (Windows), whichever matches your release line, or a later version.
  2. Update Host to 15.82 or 15.64.8 (Legacy Windows 7 & 8) or 14.7.48855 (Windows) or 13.2.36230 (Windows), whichever matches your release line, or a later version.
  3. Read the advisory on teamviewer.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
TeamViewerFull Client15.0 up to, but not including, 15.82; 15.64.0 (Legacy Windows 7 & 8) up to, but not including, 15.64.8 (Legacy Windows 7 & 8); 14.7.0 (Windows) up to, but not including, 14.7.48855 (Windows); 13.2.0 (Windows) up to, but not including, 13.2.36230 (Windows); 14.7.0 (Linux) up to, but not including, 14.7.48855 (Linux); 13.2.0 (Linux) up to, but not including, 13.2.153995 (Linux); 14.7.0 (MacOS) up to, but not including, 14.7.48855 (MacOS); 13.2.0 (MacOS) up to, but not including, 13.2.153994 (MacOS)15.82, 15.64.8 (Legacy Windows 7 & 8), 14.7.48855 (Windows), 13.2.36230 (Windows), 14.7.48855 (Linux), 13.2.153995 (Linux)
TeamViewerHost15.0 up to, but not including, 15.82; 15.64.0 (Legacy Windows 7 & 8) up to, but not including, 15.64.8 (Legacy Windows 7 & 8); 14.7.0 (Windows) up to, but not including, 14.7.48855 (Windows); 13.2.0 (Windows) up to, but not including, 13.2.36230 (Windows); 14.7.0 (Linux) up to, but not including, 14.7.48855 (Linux); 13.2.0 (Linux) up to, but not including, 13.2.153995 (Linux); 14.7.0 (MacOS) up to, but not including, 14.7.48855 (MacOS); 13.2.0 (MacOS) up to, but not including, 13.2.153994 (MacOS)15.82, 15.64.8 (Legacy Windows 7 & 8), 14.7.48855 (Windows), 13.2.36230 (Windows), 14.7.48855 (Linux), 13.2.153995 (Linux)

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (teamviewer.com).

Official description

Improper path validation in the local IPC service of TeamViewer Full Client and Host on Windows, Linux, and macOS prior to version 15.82 allows a local authenticated user with low privileges to perform arbitrary file writes with elevated privileges (NT AUTHORITY/SYSTEM \ root). By sending crafted IPC commands to the local service daemon, an attacker could manipulate file paths, leading to local privilege escalation.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

How developers prevent this class of flaw

  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.

More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Full Client

All Full Client vulnerabilities

Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities

Spotted an error? Tell us.