# CVE-2025-2183: GlobalProtect App: Improper Certificate Validation Leads to Privilege Escalation

> Attackers can bypass certificate validation to install malicious root certificates and signed software, leading to privilege escalation on endpoints.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/AU:N/R:U/V:D/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-v76x-c74h-522h

## What is CVE-2025-2183?

CVE-2025-2183 is a medium-severity vulnerability in Palo Alto Networks Global Protect UWP App, published on 13 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An insufficient certificate validation issue in the Palo Alto Networks GlobalProtect™ app enables attackers to connect the GlobalProtect app to arbitrary servers. This can enable a local non-administrative operating system user or an attacker on the same subnet to install malicious root certificates on the endpoint and subsequently install malicious software signed by the malicious root certificates on that endpoint.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2025-2183 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2183 is a medium-severity vulnerability in Palo Alto Networks Global Protect UWP App, published on 13 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-2183 in the wild and no public exploit code.

Affected product: Palo Alto Networks Global Protect UWP 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-2183/ (Markdown: https://insights.sbomify.com/CVE-2025-2183/index.md)
```

## Sources

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

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