How severe is CVE-2026-0299?

CVE-2026-0299 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2026-0299?

CVE-2026-0299 affects the following products: paloaltonetworks globalprotect.

How do I patch CVE-2026-0299?

Apply the paloaltonetworks globalprotect security patch or hotfix for CVE-2026-0299 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2026-0299 across my infrastructure?

Inventory every paloaltonetworks globalprotect deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2026-0299 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2026-0299?

O3 detects and blocks CVE-2026-0299 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2026-0299 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-0299 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2026-0299?

CVE-2026-0299 is classified as CWE-426 (CWE-426). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2026-0299?

CVE-2026-0299 affects paloaltonetworks globalprotect (2 versions, e.g. 6.2.8, 6.3.3). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2026-0299 published, and has it been updated?

CVE-2026-0299 was published on August 13, 2026 and was last updated on September 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

HIGH severity

CVE-2026-0299

HIGH

CVE-2026-0299 is a high-severity (CVSS 7.8) CWE-426 vulnerability in paloaltonetworks globalprotect. O3 Security detects and blocks CVE-2026-0299 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

Local privilege escalation vulnerabilities in the Palo Alto Networks GlobalProtect™ app enable a local user to escalate their privileges to NT AUTHORITY\SYSTEM on Windows, and root…

Published

Aug 13, 2026

Updated

Sep 3, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Sep 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-0299.

Description

Local privilege escalation vulnerabilities in the Palo Alto Networks GlobalProtect™ app enable a local user to escalate their privileges to NT AUTHORITY\SYSTEM on Windows, and root on macOS and Linux. This enables a non-administrative user to execute arbitrary commands with administrative privileges.

The GlobalProtect app on iOS, Android, and Chrome OS is not affected.

Affected Products

1 product · 57 configurations

Application

globalprotectpaloaltonetworks

≥ 6.3.0 && < 6.3.3

2 versions

6.2.86.3.3

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every paloaltonetworks globalprotect deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the paloaltonetworks globalprotect security patch or hotfix for CVE-2026-0299 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2026-0299 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2026-0299. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2026-0299 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2026-0299 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works