dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-23572

HIGH · 7.2 CVSS v3.1 Published 2026-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Improper access control in the TeamViewer Full and Host clients (Windows, macOS, Linux) prior version 15.74.5 allows an authenticated user to bypass additional access controls with “Allow after confirmation” configuration in a remote session. An exploit could result in unauthorized access prior to local confirmation. The user needs to be authenticated for the remote session via ID/password, Session Link, or Easy Access as a prerequisite to exploit this vulnerability.

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

TeamViewer Full and Host clients prior to version 15.74.5 contain an improper access control vulnerability where an authenticated remote user can bypass the 'Allow after confirmation' security setting. This allows unauthorized actions to be performed in a remote session before the local user can confirm or deny the request, despite the intended security control requiring local confirmation.

MitigationUpdate TeamViewer clients (Full and Host) to version 15.74.5 or later on all Windows, macOS, and Linux systems to remediate this access control bypass.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed TeamViewer version
    Open TeamViewer, go to Help > About TeamViewer to view the version number. On Windows, alternatively check the registry at HKEY_LOCAL_MACHINE\SOFTWARE\TeamViewer for Version. On macOS, check /Applications/TeamViewer.app/Contents/Info.plist for CFBundleShortVersionString.
    Affected if Version is present and lower than 15.74.5
  2. Confirm product is TeamViewer Full or Host
    In the TeamViewer main window, check the product name displayed. The window title or welcome screen typically shows 'TeamViewer' for Full or 'TeamViewer Host' for Host variants.
    Affected if Product is TeamViewer Full or TeamViewer Host (vulnerability applies only to these)
  3. Verify 'Allow after confirmation' setting is enabled
    In TeamViewer, go to Extras > Options > Security > Confirm remote access. Examine whether the 'Allow after confirmation' option is enabled. The vulnerability specifically bypasses this security control.
    Affected if 'Allow after confirmation' setting is enabled (the bypass only affects this specific setting)

Environment is affected if running TeamViewer Full or Host version prior to 15.74.5 with the 'Allow after confirmation' security setting enabled.

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

Update TeamViewer clients (Full and Host) to version 15.74.5 or later on all Windows, macOS, and Linux systems to remediate this access control bypass.

Recommended fix High confidence

TeamViewer 15.74.5 or later

  1. Verify current TeamViewer version by opening TeamViewer and checking Help > About TeamViewer
  2. Download TeamViewer version 15.74.5 or later from the official TeamViewer website (www.teamviewer.com)
  3. Close any active TeamViewer connections and ensure the application is not running
  4. Run the TeamViewer installer for the new version
  5. Follow the on-screen installation prompts to complete the upgrade
  6. After installation, verify the version is 15.74.5 or later via Help > About TeamViewer
  7. Ensure "Allow after confirmation" settings are properly configured in Extras > Options > Security > Advanced for any remote access policies

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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