dbcve.org
GlobalprotectApplication · Paloaltonetworks

CVE-2026-0250

HIGH · 8.1 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 6.0.12 / 6.0.13 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A buffer overflow vulnerability in the Palo Alto Networks GlobalProtect app (Windows/macOS/Linux) allows a man-in-the-middle attacker to disrupt system processes and potentially execute arbitrary code with SYSTEM privileges during Portal-Gateway request/response processing.

MitigationApply the vendor-supplied patch for GlobalProtect when available. Until then, mitigate by restricting network access to trusted GlobalProtect infrastructure and avoiding untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GlobalprotectApplication
Affected:>= 6.0.0, < 6.0.12>= 6.0.0, < 6.0.13>= 6.0.0, < 6.0.15>= 6.1.0, < 6.1.14>= 6.2.0, < 6.2.8>= 6.3.0, < 6.3.3>= 6.3.0, < 6.3.4= 6.2.8= 6.3.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify GlobalProtect app installation
    Check if the Palo Alto Networks GlobalProtect application is installed on the system. On Windows, look for the program in Add/Remove Programs or check C:\Program Files\Palo Alto Networks\GlobalProtect. On macOS, check /Applications for GlobalProtect.app.
    Affected if GlobalProtect is installed and running on the system.
  2. Determine installed GlobalProtect version
    Locate the version information. On Windows, right-click the GlobalProtect tray icon and select About, or check the program's properties. On macOS, right-click GlobalProtect.app and select Get Info. Compare the version against the affected ranges: 6.0.0 through 6.0.11, 6.0.12 through 6.0.14, 6.1.0 through 6.1.13, 6.2.0 through 6.2.7, 6.3.0 through 6.3.2, and specific versions 6.2.8 and 6.3.3.
    Affected if The installed version falls within any of the affected version ranges.
  3. Confirm Portal or Gateway configuration exists
    Check if GlobalProtect is configured to connect to a Portal or Gateway. Examine the GlobalProtect settings panel (accessed via the tray icon), or inspect configuration files in the GlobalProtect installation directory for defined portal or gateway addresses.
    Affected if GlobalProtect is configured with a Portal or Gateway connection, enabling the vulnerable communication pathway between these components.
  4. Verify network exposure to potential MITM
    Determine if the system is on a network where a man-in-the-middle attack is plausible, such as public WiFi, shared network segments, or corporate networks with multiple access points. Check network adapter configurations and connectivity.
    Affected if The system connects to networks where an attacker could intercept traffic between the GlobalProtect client and the Portal/Gateway (untrusted or shared networks).

If GlobalProtect is installed with an affected version AND is configured with an active Portal or Gateway connection on an exposed network, the environment is likely vulnerable to this buffer overflow vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.0.12 / 6.0.13 / 6.0.15 or later
Fixed in 6.0.126.0.136.0.15
Interim mitigation

Apply the vendor-supplied patch for GlobalProtect when available. Until then, mitigate by restricting network access to trusted GlobalProtect infrastructure and avoiding untrusted networks.

Recommended fix Moderate confidence

Upgrade to GlobalProtect 6.0.15 or later for 6.0.x branches; upgrade to 6.1.14 or later for 6.1.x branches

  1. 1. Identify the currently installed GlobalProtect version by checking the application's version information
  2. 2. Determine the appropriate upgrade path based on your current major version (6.0.x or 6.1.x)
  3. 3. Download the fixed GlobalProtect version from Palo Alto Networks support portal or official channels
  4. 4. Test the upgrade in a non-production environment to verify compatibility with your existing infrastructure
  5. 5. Apply the upgrade to production systems following standard change management procedures
  6. 6. Verify the upgrade was successful and GlobalProtect is functioning normally
Caveat Review Palo Alto Networks release notes for any compatibility changes between your current version and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Globalprotect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0250 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0250 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data