# CVE-2026-0327: PAN-OS: Privilege Escalation Vulnerability in GlobalProtect

Status: published. Published: 2026-11-11. Updated: 2026-11-11.

A privilege escalation vulnerability in the GlobalProtect gateway of Palo Alto Networks PAN-OS® software enables an authenticated, lower-privileged user to obtain the privileges and configuration of a higher-privileged user.



Cloud NGFW and Panorama are not affected by this vulnerability.

## Remediation

- fix: VERSION              MINOR VERSION               SUGGESTED SOLUTION
Cloud NGFW                                       No action needed.
PAN-OS 12.2          12.2.0 through 12.2.4-h*    Upgrade to 12.2.4-h2 or later.
PAN-OS 12.1          12.1.2 through 12.1.10-h*   Upgrade to 12.1.10-h4 or later.
PAN-OS 11.2          11.2.0 through 11.2.16-h*   Upgrade to 11.2.16-h2 or later.
PAN-OS 11.1          11.1.0 through 11.1.16-h*   Upgrade to 11.1.16-h5 or later.
All older                                        Upgrade to a supported fixed version.
unsupported
PAN-OS versions
Prisma Access 12.1   12.1.2 through 12.1.10-h*   Upgrade to 12.1.10-h4 or later.
Prisma Access 11.2                               Upgrade to 12.1.10-h4 or later. 


* See the note under Product Status for information regarding Prisma Access upgrades. (source: CNA: palo_alto)
- workaround: Customers can mitigate the risk of this issue by taking the following actions:

 1. Navigate to Network > GlobalProtect > Gateways (https://docs.paloaltonetworks.com/ngfw/help/10-2/globalprotect/network-globalprotect-gateways) in the management interface.
 2. Click on your Gateway Name and go to the Authentication tab.
 3. Under Client Authentication, select your existing client authentication configuration.
 4. Change the Authentication Profile to a non-challenge profile (such as SAML), or assign a Certificate Profile to enforce client certificate authentication.
 5. Click OK and Commit the changes. (source: CNA: palo_alto)

## Affected products and versions

- Palo Alto Networks / Cloud NGFW: All (unaffected, custom). Source: CNA: palo_alto
- Palo Alto Networks / PAN-OS: ≥ 12.2.0; < 12.2.4-h2 (affected, custom); unaffected at 12.2.4-h2; ≥ 12.1.0; < 12.1.10-h4 (affected, custom); unaffected at 12.1.10-h4; ≥ 11.2.0; < 11.2.16-h2 (affected, custom); unaffected at 11.2.16-h2; ≥ 11.1.0; < 11.1.16-h5 (affected, custom); unaffected at 11.1.16-h5. Source: CNA: palo_alto
- Palo Alto Networks / Prisma Access: ≥ 12.1.0; < 12.1.10-h4 (affected, custom); unaffected at 12.1.10-h4; 11.2.0 (affected, custom). Source: CNA: palo_alto

## Severity and prioritization

- CVSS 4.0: 2.3 (low); CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:U/AU:N/R:U/V:D/RE:M/U:Amber; source: CNA: palo_alto

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-426

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://security.paloaltonetworks.com/CVE-2026-0327 (CNA: palo_alto; vendor-advisory)

## Provenance

- CNA: palo_alto: https://www.cve.org/CVERecord?id=CVE-2026-0327; retrieved 2026-11-11; source updated 2026-11-11

Revision: 7ae97514bd5272dd065d33f78fd898e122f5daa6c8d9a8528a9c9b4336246dd1

Canonical: https://y2.dev/cve/CVE-2026-0327

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.