# CVE-2025-4617: Prisma Browser: Insufficient Policy Enforcement Vulnerability in Prisma Browser

> A local non-admin user can bypass screenshot controls in Prisma Browser if self-protection is not enabled.

- **Severity:** Low 1.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U/S:N/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:** 14 Nov 2025
- **Updated:** 14 Nov 2025
- **Also known as:** GHSA-gqv5-gqc6-qrch

## What is CVE-2025-4617?

CVE-2025-4617 is a low-severity vulnerability in Palo Alto Networks Prisma Browser, published on 14 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An insufficient policy enforcement vulnerability in Palo Alto Networks Prisma® Browser on Windows allows a locally authenticated non-admin user to bypass the screenshot control feature of the browser.

Browser self-protection should be enabled to mitigate this issue.

Weakness: CWE-424 (Improper Protection of Alternate Path)

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


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

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

## Is CVE-2025-4617 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4617 is a low-severity vulnerability in Palo Alto Networks Prisma Browser, published on 14 Nov 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-4617 in the wild and no public exploit code.

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

## Sources

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

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