Is CVE-2026-0324 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-0324 being exploited in the wild.

How severe is CVE-2026-0324?

Informational severity, published 11 November 2026.

Which products and versions are affected?

OPSWAT MetaDefender Endpoint Security SDK 4.3.0 to 4.3.4821 on Windows; Palo Alto Networks GlobalProtect 6.2.0 through 6.2.8-h3, 6.3.0 through 6.3.3-h2 on Windows.

Is there a fix for CVE-2026-0324?

Yes: fixed in MetaDefender Endpoint Security SDK 4.3.4822 on Windows and later; GlobalProtect 6.3.3-h3 (6.3.3-711) or later on Windows 6.3; GlobalProtect 6.2.8-h4 (6.2.8-317) or later on Windows 6.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-0324 attacked?

It is attacked with local access, in a hosted service.

Am I affected by CVE-2026-0324?

Check whether you run OPSWAT MetaDefender Endpoint Security SDK or Palo Alto Networks GlobalProtect at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-0324: Palo Alto Networks GlobalProtect privilege escalation in MetaDefender SDK

CVE-2026-0324 · Severity: info · Published 2026-11-11

A privilege escalation vulnerability exists in the OPSWAT MetaDefender Endpoint Security SDK integrated into Palo Alto Networks GlobalProtect, a VPN client used to secure remote employee access. A local user without administrative rights can exploit this flaw to gain system-level privileges, potentially enabling unauthorized access to sensitive corporate data or system compromise.

Vendors: Palo Alto Networks.

Quick answers

Is CVE-2026-0324 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-0324 being exploited in the wild.
How severe is CVE-2026-0324?: Informational severity, published 11 November 2026.
Which products and versions are affected?: OPSWAT MetaDefender Endpoint Security SDK 4.3.0 to 4.3.4821 on Windows; Palo Alto Networks GlobalProtect 6.2.0 through 6.2.8-h3, 6.3.0 through 6.3.3-h2 on Windows.
Is there a fix for CVE-2026-0324?: Yes: fixed in MetaDefender Endpoint Security SDK 4.3.4822 on Windows and later; GlobalProtect 6.3.3-h3 (6.3.3-711) or later on Windows 6.3; GlobalProtect 6.2.8-h4 (6.2.8-317) or later on Windows 6.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-0324 attacked?: It is attacked with local access, in a hosted service.
Am I affected by CVE-2026-0324?: Check whether you run OPSWAT MetaDefender Endpoint Security SDK or Palo Alto Networks GlobalProtect at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: MetaDefender Endpoint Security SDK 4.3.4822 on Windows and later; GlobalProtect 6.3.3-h3 (6.3.3-711) or later on Windows 6.3; GlobalProtect 6.2.8-h4 (6.2.8-317) or later on Windows 6.2

Technical details

The vulnerability is an incorrect privilege management flaw (CWE-266) in the MetaDefender Endpoint Security SDK on Windows that allows local escalation of privilege to NT AUTHORITY\SYSTEM. Attack vector is local with low complexity, requiring the attacker to be an authenticated non-administrative Windows user. The vulnerability has been patched in MetaDefender SDK 4.3.4822 and later versions.

Affected products

Palo Alto Networks GlobalProtect 6.2.0 through 6.2.8-h3, 6.3.0 through 6.3.3-h2 on Windows
OPSWAT MetaDefender Endpoint Security SDK 4.3.0 to 4.3.4821 on Windows

Timeline

2026-11-11: disclosed

References

https://security.paloaltonetworks.com/CVE-2026-0324

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.