CVE-2026-0250 — GlobalProtect App: Buffer Overflow Vulnerability during connection to Portal or Gateway
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Palo Alto Networks Globalprotect, Palo Alto Networks GlobalProtect App, Palo Alto Networks GlobalProtect UWP App).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Palo Alto Networks | Globalprotect |
version 6.3.3-h4version 6.3.3version 6.3.3-h1version 6.3.3-h2version 6.3.3-h3≥ 6.0.0 and < 6.0.13version 6.3.3-h6version 6.3.3-h7 and 11 moreversion 6.3.3-h8version 6.3.3-h9≥ 6.0.0 and < 6.0.12≥ 6.0.0 and < 6.0.15≥ 6.1.0 and < 6.1.14≥ 6.2.0 and < 6.2.8≥ 6.3.0 and < 6.3.3≥ 6.3.0 and < 6.3.4version 6.2.8-h7version 6.2.8-h1version 6.2.8 |
Vulnerable | NIST National Vulnerability Database |
| Palo Alto Networks | GlobalProtect App | ≥ 6.3.0 and < 6.3.3-h9 (6.3.3-999)≥ 6.2.0 and < 6.2.8-h10 (6.2.8-948)≥ 6.1 and < 6.1.13≥ 6.3.0 and < 6.3.3-h2 (6.3.3-42)≥ 6.0.0 and < 6.0.11≥ 6.0 and < 6.0.13≥ 6.0 and < 6.0.14 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Palo Alto Networks | GlobalProtect UWP App | ≥ 6.3 and < 6.3.3-h10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.2 | CVSS 4.0 | Medium | — | — | psirt@paloaltonetworks.com via NIST National Vulnerability Database |
| 5.2 | CVSS 4.0 | Medium | — | — | palo_alto via CVE Program (cve.org) e CISA ADP |
| 8.1 | CVSS 3.1 | High | 2.2 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.39%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · palo alto networks/globalprotect app, palo alto networks/globalprotect uwp app
- SSVC assessment updated
- Record published
- CVSS changed · 8.1
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-0314 GlobalProtect App: Local Denial of Service (DoS) on Windows 1d
- Medium CVE-2026-0315 GlobalProtect App: Local Privilege Escalation Vulnerability on macOS 1d
- Medium CVE-2026-0307 GlobalProtect App: Local Privilege Escalation Vulnerabilities Sep 10, 2026
- High CVE-2026-0297 GlobalProtect App: Buffer Overflow Vulnerability during UDP Tunnel Handshake Aug 13, 2026
- High CVE-2026-0298 GlobalProtect App: Code Execution Vulnerability in Windows Pre-Logon Access Provider (PLAP) Aug 13, 2026
- High CVE-2026-0299 GlobalProtect App: Local Privilege Escalation Vulnerabilities Aug 13, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-0250 is "GlobalProtect App: Buffer Overflow Vulnerability during connection to Portal or Gateway", rated High. It affects Globalprotect (Palo Alto Networks); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.1 describes technical severity. EPSS 0.39% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.