CVE-2025-0117Medium

CVE-2025-0117 GlobalProtect App: Local Privilege Escalation (PE) Vulnerability

Published
March 12, 2025
Last Modified
September 30, 2025

🔗 CVE IDs covered (1)

CVE-2025-0117 →

📋 Description

A reliance on untrusted input for a security decision in the GlobalProtect app on Windows devices potentially enables a locally authenticated non-administrative Windows user to escalate their privileges to NT AUTHORITY\SYSTEM. GlobalProtect App on macOS, Linux, iOS, Android, Chrome OS and GlobalProtect UWP App are not affected.

🎯 Affected products2

  • GlobalProtect App
  • GlobalProtect UWP App

✅ Remediation

VERSION SUGGESTED SOLUTION GlobalProtect App 6.3 on Windows Upgrade to 6.3.3 or later* GlobalProtect App 6.2 on Windows Upgrade to 6.2.6 or later* GlobalProtect App 6.1 on Windows Upgrade to 6.2.6 or later or upgrade to 6.3.3 or later* GlobalProtect App 6.0 on Windows Upgrade to 6.0.12 or later or upgrade to 6.2.6 or later or upgrade to 6.3.3 or later* GlobalProtect App on Linux No action needed GlobalProtect App on macOS No action needed GlobalProtect App on iOS No action needed GlobalProtect App on Android No action needed GlobalProtect UWP App No action needed * In addition to the software updates listed above, additional steps are required to protect against this vulnerability as described below. ** These steps are not needed for GlobalProtect app 6.2.8-h3 (6.2.8-c263) and later versions of GlobalProtect 6.2. Solution for new and existing GlobalProtect app installation on Windows You can use your endpoint mobile device management (MDM) tools to apply the following changes: 1. Install a fixed version of the GlobalProtect app. 2. Update the following registry key with the specified value (uses the REG_SZ type): [HKEY_LOCAL_MACHINE\SOFTWARE\Palo Alto Networks\GlobalProtect\Settings] "check-communication"="yes" 3. Restart the operating system to apply this registry change. Alternate solution for new GlobalProtect app installation on Windows Install the GlobalProtect app with the pre-deployment key CHECKCOMM set to "yes": > msiexec.exe /i GlobalProtect64.msi CHECKCOMM="yes" Note: This command adds the registry value from the previous solution instructions—no additional MSI options are needed. Workarounds and mitigations: No workaround or mitigation is available.

🔗 References (1)