CVE-2026-0249
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 · uneditedMultiple improper certificate validation vulnerabilities in the Palo Alto Networks GlobalProtect™ app enables an attacker to intercept encrypted communications and potentially compromise the endpoint. This can enable a local non-administrative operating system user or an attacker on the same subnet to redirect traffic to an unauthorized server and facilitate the installation of malicious software. The GlobalProtect app on Linux, Windows, iOS and GlobalProtect UWP app are 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 confidenceImproper certificate validation in the Palo Alto Networks GlobalProtect app allows local non-administrative users or adjacent network attackers to perform man-in-the-middle attacks, redirecting VPN traffic to malicious servers and potentially installing malware. The vulnerability stems from the app failing to properly validate SSL/TLS certificates, enabling traffic interception despite encrypted communications.
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>= 6.0.0, < 6.0.13>= 6.0.0, < 6.0.14>= 6.1.0, < 6.1.14>= 6.2.0, < 6.2.8>= 6.3.0, < 6.3.3= 6.2.8= 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Identify GlobalProtect app versionCheck the installed version of the Palo Alto Networks GlobalProtect app on the target system. This can typically be done through the app's UI (Help > About), the Windows Programs and Features list, or by querying the installed software via system management tools.Affected if The installed version falls within any of these ranges: 6.0.0 through 6.0.12, 6.1.0 through 6.1.13, 6.2.0 through 6.2.7 (or exactly 6.2.8), 6.3.0 through 6.3.2 (or exactly 6.3.3). Versions 6.0.13+, 6.1.14+, 6.2.9+, and 6.3.4+ are NOT affected.
-
Confirm certificate validation is in useVerify that SSL/TLS certificate validation is enabled or expected to be enforced for GlobalProtect VPN connections. This is typically a default setting in the app or configured via gateway policies.Affected if The app is configured to validate SSL/TLS certificates for VPN connections. The vulnerability exists specifically because improper validation occurs - if validation is disabled entirely, the attack vector differs.
-
Check for MITM exposure indicatorsReview network logs or packet captures from the GlobalProtect client to identify any connection anomalies, unexpected certificate warnings, or connections to unfamiliar gateway addresses. Examine whether traffic is being redirected to unexpected IP addresses.Affected if Connections are being routed through unexpected servers or certificates do not match expected gateway identities, indicating potential exploitation of the validation flaw.
You are affected if the installed GlobalProtect version is 6.0.0-6.0.12, 6.1.0-6.1.13, 6.2.0-6.2.8, or 6.3.0-6.3.3 and the app validates SSL/TLS certificates for VPN 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.136.0.146.1.14
Apply the vendor-provided patch or update to the GlobalProtect app to remediate the certificate validation flaws. Verify that certificate chain validation is enforced and test that traffic is properly routed through legitimate VPN gateways.
GlobalProtect 6.0.14 (for 6.0.x users), 6.1.14 (for 6.1.x users), or 6.2.8 (for 6.2.x users)
- Identify the currently installed GlobalProtect version by checking the application or system information
- Determine which version branch your current installation belongs to (6.0.x, 6.1.x, or 6.2.x)
- For version 6.0.x: Upgrade to version 6.0.14 or later
- For version 6.1.x: Upgrade to version 6.1.14 or later
- For version 6.2.x: Upgrade to version 6.2.8 or later
- After upgrading, verify the certificate validation is working correctly by testing VPN connections
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0249 — 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-2026-0249 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