CVE-2026-0297GlobalProtect App: Buffer Overflow Vulnerability during UDP Tunnel Handshake
- 5.2MediumCVSS base score
- 0.60%Exploitation in 30 daysEPSS · top 51% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
A buffer overflow vulnerability exists in the Palo Alto Networks GlobalProtect™ app that enables a man-in-the-middle (MitM) attacker or a rogue gateway to disrupt system processes and potentially execute arbitrary code with elevated privileges (SYSTEM privileges on Windows, and root privileges on macOS and Linux).
Timeline
ID reserved
By palo_alto
- 9 months later
· 9 months later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| palo_altoCNA (assigner) | 4.0 | Medium5.2 | CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/AU:N/R:U/V:D/RE:M/U:Amber |
| NVDNVD · Undergoing Analysis | 4.0 | Medium5.2 | CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:M/U:Amber |
- EPSS (exploitation in 30 days)
- 0.60% · top 51% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.2.
Affected products
Palo Alto Networks · GlobalProtect App
- affected 6.3.0 – < 6.3.3-h15
- affected 6.2.0
- affected 6.0.0 – < 6.0.15
Palo Alto Networks · GlobalProtect App
- affected 6.3.0 – < 6.3.3-h14
- affected 6.2.0 – < 6.2.8-h13
- affected 6.0.0 – < 6.0.15
Palo Alto Networks · GlobalProtect App
- affected 6.3.0 – < 6.3.5
- affected 6.0.0 – < 6.0.15
What to do
Solution: VERSION MINOR VERSION SUGGESTED SOLUTION GlobalProtect App 6.3/6.2 on Linux 6.2.0 through 6.3.3-h14 Upgrade to 6.3.3-h15 or later. GlobalProtect App 6.0 on Linux 6.0.0 through 6.0.14 Upgrade to 6.0.15 or later. GlobalProtect App 6.3 on macOS 6.3.0 through 6.3.3-h13 Upgrade to 6.3.3-h14 (6.3.3-1121) or later. GlobalProtect App 6.2 on macOS 6.2.0 through 6.2.8-h12 Upgrade to 6.2.8-h13 (6.2.8-1045) or later. GlobalProtect App 6.0 on macOS 6.0.0 through 6.0.14 Upgrade to 6.0.15 or later. GlobalProtect App 6.3 on Windows 6.3.0 through 6.3.3-h13 Upgrade to 6.3.3-h14 (6.3.3-1121) or later. GlobalProtect App 6.2 on Windows 6.2.0 through 6.2.8-h12 Upgrade to 6.2.8-h13 (6.2.8-1045) or later. GlobalProtect App 6.0 on Windows 6.0.0 through 6.0.14 Upgrade to 6.0.15 or later. GlobalProtect App 6.3/6.1 on iOS 6.1.0 through 6.3.4 Upgrade to 6.3.5 or later. GlobalProtect App 6.0 on iOS 6.0.0 through 6.0.14 Upgrade to 6.0.15 or later. GlobalProtect App 6.3/6.1 on Android 6.1.0 through 6.3.4 Upgrade to 6.3.5 or later. GlobalProtect App 6.0 on Android 6.0.0 through 6.0.14 Upgrade to 6.0.15 or later. GlobalProtect App 6.3/6.1 on ChromeOS 6.1.0 through 6.3.4 Upgrade to 6.3.5 or later. GlobalProtect App 6.0 on ChromeOS 6.0.0 through 6.0.14 Upgrade to 6.0.15 or later.
Workaround: Customers can mitigate the risk of this issue by taking either of the following three actions: 1. Enforce SSL-Only VPN Connections: Modify your GlobalProtect Portal configurations to disable IPSec/UDP tunneling, forcing the client applications to connect exclusively via SSL VPN mode. Customer can configure Connect with SSL Only (https://docs.paloaltonetworks.com/globalprotect/administration/globalprotect-portals/customize-the-globalprotect-app) tunnel by configuring ' Advanced Control for Tunnel Mode Behavior' on GlobalProtect Portal Network > Portal > Agent Configuration> Advanced Control for Tunnel Mode Behavior 2. Customers can configure SSL only tunnel protocol by un-checking 'Enable IPSec (https://docs.paloaltonetworks.com/ngfw/help/10-2/globalprotect/network-globalprotect-gateways/globalprotect-gateways-agent-tab/tunnel-settings-tab)' on GlobalProtect gateway at Network > Gateway > Agent > Tunnel Setting > Enable IPSec 3. Workaround for new and existing GlobalProtect app >= 6.2.8 or GlobalProtect app >= 6.3.3 installations on Windows and macOS GlobalProtect 6.2.8 and GlobalProtect app 6.3.3 on Windows and macOS introduce a new configuration Enable Strict Certificate Check (https://docs.paloaltonetworks.com/platform-explorer?productCategoryTags=pan%3Aproductcategory%2Fglobalprotect) which enables certificate checks required to mitigate this issue on Windows and macOS. This configuration only takes effect after the first connection between the GlobalProtect client and the GlobalProtect portal. Therefore the first connection is not protected. To ensure that the first connection is also protected, additionally follow the steps noted below for GlobalProtect < 6.2.8. This configuration option is currently not available for the GlobalProtect app on platforms other than Windows and macOS. Workaround for new and existing GlobalProtect app < 6.2.8 or GlobalProtect app < 6.3.3 installations on macOS 1. Use Xcode to edit the com.paloaltonetworks.GlobalProtect.settings.plist file (https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-apps/deploy-app-settings-transparently/deploy-app-settings-to-mac-endpoints/deploy-app-settings-in-the-mac-plist) in /Library/Preferences. 2. Add a "Settings" section if it does not exist within the GlobalProtect section. 3. Within the "Settings" section, add the full-chain-cert-verify key and set the string value to yes 4. Restart macOS. <key>GlobalProtect</key> <dict> (removed for brevity) <key>Settings</key> <dict> <key>full-chain-cert-verify</key> <string>yes</string> </dict> </dict> Workaround for new and existing GlobalProtect app installations on Linux 1. Create the /opt/paloaltonetworks/globalprotect/pangps.xml pre-deployment configuration file. 2. Add the pre-deployment settings to the pangps.xml file <GlobalProtect> <Settings> <full-chain-cert-verify>yes</full-chain-cert-verify> </Settings </GlobalProtect> Workaround for new and existing GlobalProtect app installations on Android, iOS and ChromeOS Customers can use their endpoint mobile device management (MDM) tools to apply the following changes 1. Set the key "full-chain-cert-verify"="yes".
Exploitation: Palo Alto Networks is not aware of any malicious exploitation of this issue.
References
References1
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-57711 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-0297)Record last updated .