dbcve.org
QsnapperApplication · Presire

CVE-2026-41045

HIGH · 7.0 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 1.3.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A time-to-check-time-of-use (TOCTOU) race condition exists in the polkit authentication implementation of qSnapper before version 1.3.3. An attacker can exploit the window between when authentication is checked and when it is used to bypass the authentication mechanism and execute operations with elevated privileges.

MitigationUpgrade qSnapper to version 1.3.3 or later. If unable to upgrade, review polkit integration code to eliminate the race condition window between authentication verification and privilege escalation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
QsnapperApplication
Affected:< 1.3.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify qSnapper is installed
    Check for qSnapper binary or service on the system using commands such as: which qsnapper, dpkg -l | grep qsnapper, rpm -qa | grep qsnapper, or by listing running processes for qsnapper
    Affected if qSnapper is not present on the system (not affected)
  2. Identify installed qSnapper version
    Run qsnapper --version or check the package manager query output (dpkg -l qsnapper, rpm -qi qsnapper) to retrieve the exact version number
    Affected if Version is lower than 1.3.3 (for example 1.3.2, 1.3.1, 1.0.x)
  3. Confirm polkit integration is in use
    Examine qSnapper configuration files (typically in /etc/qsnapper/ or ~/.config/qsnapper/) and look for polkit-related settings, or inspect running processes for polkit daemon interaction during qSnapper operations
    Affected if qSnapper uses polkit for authentication and the version is below 1.3.3
  4. Review polkit policy for qSnapper
    Check for polkit policy files in /usr/share/polkit-1/actions/ or /etc/polkit-1/localauthority/ that reference qSnapper operations, and note whether qSnapper performs privileged operations through polkit
    Affected if A polkit policy exists that allows qSnapper to perform elevated operations and the qSnapper version is below 1.3.3

A system is affected if qSnapper with polkit authentication integration is installed and the installed version is below 1.3.3, creating the window for TOCTOU exploitation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.3.3 or later
Fixed in 1.3.3
Interim mitigation

Upgrade qSnapper to version 1.3.3 or later. If unable to upgrade, review polkit integration code to eliminate the race condition window between authentication verification and privilege escalation.

Recommended fix High confidence

1.3.3

  1. Identify the current installed version of qSnapper using your system's package manager or 'rpm -q qsnapper' or 'dpkg -l qsnapper'
  2. Update the package repository to ensure you have access to the latest packages
  3. Upgrade qSnapper to version 1.3.3 or later using 'zypper update qsnapper' (for openSUSE/SUSE) or 'dnf update qsnapper' (for Fedora/RHEL-based)
  4. Verify the installed version is 1.3.3 or higher using 'rpm -q qsnapper' or checking the package details
  5. Test that qSnapper functions correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qsnapper Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41045 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41045 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data