# CVE-2026-59678: Missing authorization in PortProtonQt

> Attackers can mount arbitrary file systems and modify network settings due to missing authorization checks in PortProtonQt.

- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-7h94-344f-429f, openSUSE-SU-2026:11969-1

## What is CVE-2026-59678?

CVE-2026-59678 is a high-severity missing authorization vulnerability in Linux-Gaming PortProtonQt, published on 23 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Incorrect Authorization vulnerability in Linux-Gaming PortProtonQt allows any users to mount and unmount arbitrary file systems and modify the network configuration via NetworkManager.

This issue affects PortProtonQt before 0d0f0950ebd948cdf82e8c3e1ebd2bcb9b8bafbe.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-59678?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `portprotonqt` | openSUSE:Tumbleweed | All versions | 1.4.1-1.1 |

## How do I fix CVE-2026-59678?

Apply the vendor's patch.

## Is CVE-2026-59678 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59678 and fix it if it is affected.

What it is: CVE-2026-59678 is a high-severity missing authorization vulnerability in Linux-Gaming PortProtonQt, published on 23 Jul 2026. 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-2026-59678 in the wild and no public exploit code.

Affected product: Linux-Gaming PortProtonQt. 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-2026-59678/ (Markdown: https://insights.sbomify.com/CVE-2026-59678/index.md)
```

## Sources

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

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