Quick answers
- Is CVE-2026-41045 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41045 being exploited in the wild.
- How severe is CVE-2026-41045?
- High severity, with a CVSS score of 8.1, published 22 June 2026.
- Which products and versions are affected?
- Presire qSnapper < 1.3.3.
- Is there a fix for CVE-2026-41045?
- A patch was published on 2026-05-25: Upstream release 1.3.3 published with fixes. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41045 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-41045?
- Check whether you run Presire qSnapper at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A TOCTOU (Time-of-Check Time-of-Use) vulnerability exists in qSnapper's D-Bus service before version 1.3.3. The `SnapshotOperations::checkAuthorization()` function utilizes Polkit's `UnixProcess` subject, which relies on PIDs for authentication. Because PIDs can be recycled, a local attacker can initiate a request and, through a race condition, ensure that by the time `polkitd` checks the requester's identity, the PID has been reassigned to a privileged process. This allows the attacker to bypass Polkit policies and execute D-Bus methods as root. The issue was resolved in version 1.3.3 by migrating to the race-free `SystemBusName` subject.
Affected products
- presire qSnapper < 1.3.3
Timeline
- 2026-04-09: disclosed: Initial discovery and internal reporting by SUSE security team.
- 2026-05-25: patched: Upstream release 1.3.3 published with fixes.
- 2026-06-22: advisory: CVE-2026-41045 published to NVD.