# CVE-2025-50327: Security feature bypass in n/a

> Remote attackers can bypass Mark-of-the-Web protection in ZPAQFRANZ to execute arbitrary code and escalate privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-4mx5-j7xw-v5rc, UBUNTU-CVE-2025-50327, openSUSE-SU-2026:11483-1

## What is CVE-2025-50327?

CVE-2025-50327 is a high-severity vulnerability in n/a, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue in Franco Corbelli ZPAQFRANZ v.61.3 and before allows a remote attacker to escalate privileges and execute arbitrary code via a bypass of the Mark-of-the-Web protection mechanism

Weakness: CWE-693 (Protection Mechanism Failure)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zpaqfranz` | openSUSE:Tumbleweed | All versions | 64.8-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2025-50327 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50327 is a high-severity vulnerability in n/a, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-50327 in the wild and no public exploit code.

Affected product: n/a. 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-50327/ (Markdown: https://insights.sbomify.com/CVE-2025-50327/index.md)
```

## Sources

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

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