CVE-2025-36537
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 · uneditedIncorrect Permission Assignment for Critical Resource in the TeamViewer Client (Full and Host) of TeamViewer Remote and Tensor prior Version 15.67 on Windows allows a local unprivileged user to trigger arbitrary file deletion with SYSTEM privileges via leveraging the MSI rollback mechanism. The vulnerability only applies to the Remote Management features: Backup, Monitoring, and Patch Management.
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 confidenceTeamViewer Client for Windows prior to version 15.67 has an incorrect permission assignment vulnerability in its MSI rollback mechanism. A local unprivileged user can exploit this to trigger arbitrary file deletion with SYSTEM privileges, specifically targeting the Remote Management features (Backup, Monitoring, and Patch Management).
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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/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.
-
Verify TeamViewer installationSearch for TeamViewer in the Windows Registry under HKLM\SOFTWARE\TeamViewer (or HKLM\SOFTWARE\Wow6432Node\TeamViewer for 32-bit on 64-bit systems), or locate the TeamViewer.exe executable in C:\Program Files\TeamViewer\ or C:\Program Files (x86)\TeamViewer\Affected if TeamViewer Client for Windows is installed on the system
-
Retrieve installed versionRead the Version value from the Windows Registry key HKLM\SOFTWARE\TeamViewer\Version (or the Wow6432Node equivalent), or right-click TeamViewer.exe in the installation folder and view the File Version in the Details tabAffected if Installed version exists and is lower than 15.67
-
Check Remote Management configurationOpen TeamViewer, go to Extras > Options > Remote Management, or check the Windows Registry under HKLM\SOFTWARE\TeamViewer\RemoteManagement for enabled featuresAffected if any Remote Management feature (Backup, Monitoring, or Patch Management) is enabled
The system is affected if TeamViewer Client for Windows version is below 15.67 AND at least one Remote Management feature (Backup, Monitoring, or Patch Management) is enabled, as the MSI rollback permission flaw requires these features to be active for exploitation.
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 · scopedUpgrade TeamViewer Client (Full and Host) to version 15.67 or later to remediate this local privilege escalation vulnerability.
TeamViewer version 15.67 or later
- 1. Verify the current TeamViewer version by opening TeamViewer and checking About > Version
- 2. Download TeamViewer version 15.67 or later from the official TeamViewer website (www.teamviewer.com)
- 3. Ensure any Remote Management features (Backup, Monitoring, Patch Management) are noted for testing after upgrade
- 4. Run the TeamViewer installer with appropriate permissions
- 5. Restart the TeamViewer service if required
- 6. Verify the upgrade was successful by checking the version number again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36537 — 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-36537 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