Palo Alto discloses GlobalProtect Windows privilege escalation CVE-2026-0324
Palo Alto Networks says CVE-2026-0324 in the OPSWAT SDK inside GlobalProtect on Windows allows local SYSTEM escalation; upgrade the app.
- Published
- Fixed in
- GlobalProtect App 6.3.3-h3 (6.3.3-711) or later, GlobalProtect App 6.2.8-h4 (6.2.8-317) or later, OPSWAT MetaDefender Endpoint Security SDK 4.3.4822 or later
- Exploitation
- No, Palo Alto Networks says it is not aware of any malicious exploitation
Live scores
CVE-2026-0324- EPSS
- 0.001
low predicted chance of attack - VEDAS
- 0.051
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Out of scope (local)
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-0327- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.047
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
What happened
According to its own security advisory, Palo Alto Networks discloses an incorrect privilege management vulnerability, CVE-2026-0324, in the OPSWAT MetaDefender Endpoint Security SDK that the GlobalProtect app uses on Windows. Palo Alto Networks says a locally authenticated, non-administrative Windows user could escalate privileges to NT AUTHORITY\SYSTEM. Palo Alto PSIRT
The advisory was published on 2026-11-11 and says the issue was discovered externally. Palo Alto Networks thanks Sandro Poppi for discovering and reporting it. Palo Alto PSIRT
Palo Alto Networks rates it Medium, with a CVSS-BT score of 5.9 and a CVSS-B score of 8.5, and a suggested urgency of Moderate. It lists the attack vector as local, the privileges required as low, and exploit maturity as unreported. It says it is not aware of any malicious exploitation. Palo Alto PSIRT
What is not confirmed: the sources contain no independent verification beyond the vendor advisory, and no technical details of the flaw beyond the weakness type the vendor lists (CWE-266). Details of how it could be abused are not confirmed.
Am I affected?
According to Palo Alto Networks, the affected component is the MetaDefender Endpoint Security SDK on Windows, versions 4.3.0 up to but not including 4.3.4822. No special configuration is required to be affected. Palo Alto PSIRT
For the GlobalProtect app on Windows, the vendor lists these affected ranges:
- GlobalProtect App 6.3 on Windows: 6.3.0 through 6.3.3-h2.
- GlobalProtect App 6.2 on Windows: 6.2.0 through 6.2.8-h3.
The vendor says no action is needed for GlobalProtect on macOS, Linux, iOS, Android, or for the GlobalProtect UWP app. Palo Alto PSIRT
Palo Alto Networks published a separate advisory the same day for CVE-2026-0327, a PAN-OS GlobalProtect gateway issue that it rates Low. It is a different flaw with different fixed versions and is not covered here. Palo Alto PSIRT
What to do now
- Identify Windows endpoints running the GlobalProtect app and check their version against the ranges above.
- Upgrade GlobalProtect App 6.3 on Windows to 6.3.3-h3 (6.3.3-711) or later, as Palo Alto Networks advises. Palo Alto PSIRT
- Upgrade GlobalProtect App 6.2 on Windows to 6.2.8-h4 (6.2.8-317) or later. These versions include the updated SDK 4.3.4822. Palo Alto PSIRT
- Plan for the upgrade rather than a workaround: the vendor states no known workarounds or mitigations exist. Palo Alto PSIRT
- Review the separate CVE-2026-0327 advisory if you run PAN-OS with a GlobalProtect gateway. Palo Alto PSIRT