GlobalProtect App: Out-of-bounds Write
CVE-2026-0250 is a high-severity out-of-bounds write vulnerability in GlobalProtect App from Palo Alto Networks, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 6.3.3-h9 (6.3.3-999), 6.2.8-h10 (6.2.8-948), 6.1.13 as the first without the flaw, so updating GlobalProtect App to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.39% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update GlobalProtect App to 6.3.3-h9 (6.3.3-999) or 6.2.8-h10 (6.2.8-948) or 6.1.13 or 6.3.3-h2 (6.3.3-42), whichever matches your release line, or a later version.
- Update GlobalProtect UWP App to 6.3.3-h10 or a later version.
- Update Globalprotect to 6.0.12 or 6.0.13 or 6.0.15 or 6.1.14, whichever matches your release line, or a later version.
- Read the advisory on security.paloaltonetworks.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Palo Alto Networks | GlobalProtect App | 6.3.0 up to, but not including, 6.3.3-h9 (6.3.3-999); 6.2.0 up to, but not including, 6.2.8-h10 (6.2.8-948); 6.1 up to, but not including, 6.1.13; 6.3.0 up to, but not including, 6.3.3-h2 (6.3.3-42); 6.0.0 up to, but not including, 6.0.11; 6.0 up to, but not including, 6.0.13; 6.0 up to, but not including, 6.0.14 | 6.3.3-h9 (6.3.3-999), 6.2.8-h10 (6.2.8-948), 6.1.13, 6.3.3-h2 (6.3.3-42), 6.0.11, 6.0.13 |
| Palo Alto Networks | GlobalProtect UWP App | 6.3 up to, but not including, 6.3.3-h10 | 6.3.3-h10 |
| Palo Alto Networks | Globalprotect | 6.0.0 up to, but not including, 6.0.12; 6.0.0 up to, but not including, 6.0.13; 6.0.0 up to, but not including, 6.0.15; 6.1.0 up to, but not including, 6.1.14; 6.2.0 up to, but not including, 6.2.8; 6.3.0 up to, but not including, 6.3.3; 6.3.0 up to, but not including, 6.3.4; 6.2.8; and 1 more ranges | 6.0.12, 6.0.13, 6.0.15, 6.1.14, 6.2.8, 6.3.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 5.2 | Medium | CNA (paloaltonetworks.com) |
| CVSS 3.1 | 8.1 | High | NVD |
Official description
A buffer overflow vulnerability exists in the Palo Alto Networks GlobalProtect™ app that enables a man in the middle attacker to disrupt system processes and potentially execute arbitrary code with SYSTEM privileges. This vulnerability is triggered during the processing of requests and responses exchanged between Portal and Gateway. The GlobalProtect app on iOS is not affected.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in GlobalProtect App
- 7.8 High severity
- 8.1 High severity
- 8.1 High severity
- 7.4 High severity
- 7.0 High severity
- 7.8 High severity
Recent Out-of-bounds Write vulnerabilities
- 9.8 Critical severity
- 8.8 High severity
- 7.8 High severity
- 7.1 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.