# CVE-2025-0141: GlobalProtect App: Privilege Escalation (PE) Vulnerability

> A local authenticated user can escalate privileges to root or SYSTEM on macOS, Linux, and Windows via the GlobalProtect App.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H/AU:N/R:U/V:D/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-xvp4-4cr4-vjqg

## What is CVE-2025-0141?

CVE-2025-0141 is a high-severity vulnerability in Palo Alto Networks GlobalProtect App, published on 9 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An incorrect privilege assignment vulnerability in the Palo Alto Networks GlobalProtect™ App on enables a locally authenticated non administrative user to escalate their privileges to root on macOS and Linux or NT AUTHORITY\SYSTEM on Windows.

The GlobalProtect app on iOS, Android, Chrome OS and GlobalProtect UWP app are not affected.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2025-0141?


## How do I fix CVE-2025-0141?

No fix has been published for CVE-2025-0141 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0141 being exploited?

There is no known exploitation of CVE-2025-0141 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0141 and fix it if it is affected.

What it is: CVE-2025-0141 is a high-severity vulnerability in Palo Alto Networks GlobalProtect App, published on 9 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0141 in the wild and no public exploit code.

Affected product: Palo Alto Networks GlobalProtect App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0141/ (Markdown: https://insights.sbomify.com/CVE-2025-0141/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0141
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0141
- OSV: https://osv.dev/vulnerability/CVE-2025-0141

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0141/
Summaries are generated and may contain mistakes; the official description above is the record.