Skip to main content
Mallory
HighVulnerability

CVE-2026-41045: Weak polkit authentication race condition in qSnapper

Published Jun 22, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.0High · v3.1
EPSS0.16%5th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
presire
IdentifiersCVE-2026-41045CWE-367 · Time-of-check Time-of-use (TOCTOU)…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a local attacker to bypass authorization controls on qSnapper's privileged D-Bus operations and perform actions as a more privileged user, including root. This can result in compromise of confidentiality, integrity, and availability through unauthorized administrative operations. The issue can also serve as a component in exploit chains with other qSnapper flaws to achieve full local root compromise.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce exposure by restricting local access to systems running qSnapper, limiting which users can interact with the system D-Bus service, and disabling or removing qSnapper where it is not required. Additional hardening should focus on minimizing access to privileged snapshot-management functionality until the fixed release can be installed. These measures are only temporary and do not remove the underlying race condition.

Remediation

Patch, then assume compromise.

Upgrade qSnapper to version 1.3.3 or later. The fix replaces the unsafe Polkit UnixProcess-based authorization subject with the SystemBusName subject to eliminate the PID-reuse race in client identification. After upgrading, verify that the updated polkit authorization path is in use and that no older vulnerable qSnapper components remain deployed.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
presireQsnapperapplication
FAQ

Frequently asked questions

Is CVE-2026-41045 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-41045 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-41045?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-41045.
Is there a patch for CVE-2026-41045?
Upgrade qSnapper to version 1.3.3 or later. The fix replaces the unsafe Polkit UnixProcess-based authorization subject with the SystemBusName subject to eliminate the PID-reuse race in client identification.
What products are affected by CVE-2026-41045?
presire Qsnapper.
How severe is CVE-2026-41045?
CVE-2026-41045 has a CVSS v3.1 score of 7.0 (High) and an EPSS score of 0.16% (5th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.