GlobalprotectApplication · Paloaltonetworks
CVE-2025-0118
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 · uneditedA vulnerability in the Palo Alto Networks GlobalProtect app on Windows allows a remote attacker to run ActiveX controls within the context of an authenticated Windows user. This enables the attacker to run commands as if they are a legitimate authenticated user. However, to exploit this vulnerability, the authenticated user must navigate to a malicious page during the GlobalProtect SAML login process on a Windows device. This issue does not apply to the GlobalProtect app on other (non-Windows) platforms.
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 · high confidenceA vulnerability in Palo Alto Networks GlobalProtect app for Windows allows remote attackers to execute ActiveX controls within an authenticated user's context during the SAML login process. By tricking a user into visiting a malicious page during GlobalProtect SAML authentication, an attacker can run commands with the privileges of the authenticated Windows user.
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
>= 6.0.0, < 6.0.11>= 6.1.0, < 6.1.6>= 6.2.0, < 6.2.5>= 6.3.0, < 6.3.3CVSS 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
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm GlobalProtect is installed on the Windows systemCheck for GlobalProtect installation by reviewing installed programs in Windows Settings or using 'Get-ItemProperty' on the registry key 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' to locate an entry with 'GlobalProtect' in the DisplayNameAffected if GlobalProtect is not present on the system, the vulnerability does not apply
-
Identify the installed GlobalProtect versionLocate the GlobalProtect executable (typically found in 'C:\Program Files\Palo Alto Networks\GlobalProtect' or 'C:\Program Files (x86)\Palo Alto Networks\GlobalProtect') and retrieve its file version property, or query the registry key 'HKLM\SOFTWARE\Palo Alto Networks\GlobalProtect\General' for the 'Version' valueAffected if the version falls within any of these ranges: 6.0.0 through 6.0.10.x, 6.1.0 through 6.1.5.x, 6.2.0 through 6.2.4.x, or 6.3.0 through 6.3.2.x (versions less than 6.0.11, 6.1.6, 6.2.5, or 6.3.3 respectively)
-
Verify SAML authentication is configured for GlobalProtectInspect the GlobalProtect portal or gateway configuration through the PAN-OS management interface or the client configuration file (typically 'PanGPA.ini' in the GlobalProtect installation directory) for SAML-based authentication settingsAffected if SAML authentication is not configured and the system uses only certificate-based or other non-SAML authentication methods, the specific attack vector during SAML login does not apply
The system is affected if GlobalProtect for Windows is installed with a version matching one of the affected ranges AND SAML authentication is actively used for GlobalProtect connections.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.0.116.1.66.2.5
Apply vendor patches from Palo Alto Networks for GlobalProtect when available. Until then, warn users to avoid navigating to untrusted pages during the GlobalProtect SAML login process on Windows devices.
GlobalProtect 6.0.11, 6.1.6, 6.2.5, or 6.3.3 (or any later stable release)
- Identify the currently installed GlobalProtect version on Windows devices using Add/Remove Programs or the GlobalProtect UI
- Determine which version branch is currently in use (6.0.x, 6.1.x, 6.2.x, or 6.3.x)
- Download the appropriate fixed version from the Palo Alto Networks support portal based on the version branch: 6.0.11 or later for 6.0.x, 6.1.6 or later for 6.1.x, 6.2.5 or later for 6.2.x, 6.3.3 or later for 6.3.x
- Test the upgrade in a non-production environment first to ensure compatibility with existing VPN infrastructure
- Deploy the upgrade to Windows endpoints using your organization's software distribution method (e.g., Group Policy, SCCM, Intune)
- Verify the upgrade was successful by checking the GlobalProtect version after installation
- Ensure users are aware not to visit untrusted pages during the SAML login process as a defense-in-depth measure
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
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 locallyCheck whether your project pulls in CVE-2025-0118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0118 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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