CVE-2026-23572

7.2 HIGH

📋 TL;DR

This vulnerability allows authenticated TeamViewer users to bypass the 'Allow after confirmation' security setting during remote sessions. Attackers who have valid credentials can gain unauthorized access without waiting for local user confirmation. All TeamViewer Full and Host clients on Windows, macOS, and Linux are affected.

💻 Affected Systems

Products:
  • TeamViewer Full
  • TeamViewer Host
Versions: All versions prior to 15.74.5
Operating Systems: Windows, macOS, Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems with 'Allow after confirmation' configuration enabled. Requires authenticated remote session via ID/password, Session Link, or Easy Access.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise by authenticated attackers who bypass all remote access controls, potentially leading to data theft, ransomware deployment, or persistent backdoor installation.

🟠

Likely Case

Unauthorized access to systems by attackers with stolen or compromised TeamViewer credentials, enabling data exfiltration or lateral movement within networks.

🟢

If Mitigated

Limited impact if strong authentication controls, network segmentation, and monitoring are in place to detect unusual TeamViewer activity.

🌐 Internet-Facing: HIGH - TeamViewer is commonly exposed to the internet for remote access, making vulnerable instances easily discoverable and exploitable.
🏢 Internal Only: MEDIUM - Internal attackers with valid credentials could exploit this, but requires initial access to TeamViewer credentials.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW - Once authenticated, bypassing the confirmation appears straightforward based on the description.

Exploitation requires valid TeamViewer authentication credentials, which could be obtained through credential theft, phishing, or brute force attacks.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 15.74.5 and later

Vendor Advisory: https://www.teamviewer.com/en/resources/trust-center/security-bulletins/tv-2026-1003/

Restart Required: Yes

Instructions:

1. Open TeamViewer application. 2. Go to Help > Check for new version. 3. Follow prompts to update to version 15.74.5 or later. 4. Restart TeamViewer service/application.

🔧 Temporary Workarounds

Disable 'Allow after confirmation'

all

Change TeamViewer security settings to require different authentication methods instead of 'Allow after confirmation'.

TeamViewer GUI: Extras > Options > Security > Advanced Settings > Change 'Access Control' to 'Full Access' or 'Deny' instead of 'Allow after confirmation'

Implement IP whitelisting

all

Restrict TeamViewer connections to trusted IP addresses only.

TeamViewer GUI: Extras > Options > Security > Configure > Add trusted IPs to whitelist

🧯 If You Can't Patch

  • Disable TeamViewer service entirely until patching is possible
  • Implement network-level blocking of TeamViewer traffic using firewall rules

🔍 How to Verify

Check if Vulnerable:

Check TeamViewer version in Help > About. If version is below 15.74.5 and 'Allow after confirmation' is enabled, system is vulnerable.

Check Version:

TeamViewer GUI: Help > About (shows version number)

Verify Fix Applied:

Confirm version is 15.74.5 or higher in Help > About. Test remote connection with 'Allow after confirmation' to ensure proper confirmation appears.

📡 Detection & Monitoring

Log Indicators:

  • TeamViewer logs showing successful connections without corresponding 'confirmation' events
  • Multiple failed authentication attempts followed by successful connection

Network Indicators:

  • TeamViewer traffic (typically port 5938) from unexpected IP addresses
  • Unusual data transfer volumes during TeamViewer sessions

SIEM Query:

source="TeamViewer*" AND (event="connection_success" NOT event="confirmation_prompt")

🔗 References

📤 Share & Export