# CVE-2026-41045: Weak polkit authentication check in qSnapper

> A local attacker can exploit a race condition in qSnapper's polkit authentication to bypass checks and execute commands as root.

- **Severity:** High 8.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 22 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-w4qv-m9pp-3xjr

## What is CVE-2026-41045?

CVE-2026-41045 is a high-severity vulnerability in presire qSnapper, published on 22 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A time-to-check-time-of-use in polkit authentication of qSnapper before version 1.3.3 allowed a local attacker to bypass qSnappers authentication mechanism and operate e.g. as root user.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 1 product.


Products: Presire Qsnapper.

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

Upgrade to a fixed version.

## Is CVE-2026-41045 being exploited?

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

## Other vulnerabilities in presire qSnapper

- [CVE-2026-41048](https://insights.sbomify.com/CVE-2026-41048/): Caching of Authentication allows Authentication Bypass in qSnapper (high 8.4)
- [CVE-2026-41049](https://insights.sbomify.com/CVE-2026-41049/): Caching of Authentication allows Authentication Bypass between users in qSnapper (high 8.4)
- [CVE-2026-41046](https://insights.sbomify.com/CVE-2026-41046/): path traversal via `config` parameter in qSnapper (high 7.3)
- [CVE-2026-41047](https://insights.sbomify.com/CVE-2026-41047/): Information leak via “diff” methods in qSnapper (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41045 is a high-severity vulnerability in presire qSnapper, published on 22 Jun 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-41045 in the wild and no public exploit code.

Affected product: presire qSnapper. 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-41045/ (Markdown: https://insights.sbomify.com/CVE-2026-41045/index.md)
```

## Sources

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

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