CVE-2026-41045 is a local privilege-escalation vulnerability in qSnapper before version 1.3.3 caused by a time-of-check-time-of-use flaw in its polkit authorization logic. The issue affects SnapshotOperations::checkAuthorization(), which authenticates clients using Polkit's UnixProcess subject derived from the PID associated with the active D-Bus connection. Because this PID-based identity check is subject to reuse and race conditions between the time qSnapper identifies the client and the time polkit validates it, a local attacker can bypass qSnapper's intended polkit authentication checks. Successful exploitation allows unauthorized invocation of privileged operations exposed by qSnapper's root-privileged D-Bus service, including actions that can be performed with root privileges.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A local privilege escalation/authentication bypass vulnerability in qSnapper caused by a time-to-check-time-of-use flaw in polkit authentication before version 1.3.3.
A local privilege escalation/authentication bypass vulnerability in qSnapper caused by unsafe use of Polkit's UnixProcess subject, enabling a race condition via PID reuse that may let attackers bypass Polkit checks.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.