Quick answers
- Is CVE-2026-41048 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41048 being exploited in the wild.
- How severe is CVE-2026-41048?
- Informational severity, with a CVSS score of 8.4, published 22 June 2026.
- Which products and versions are affected?
- Presire qSnapper >= 1.2.1, < 1.3.3.
- Is there a fix for CVE-2026-41048?
- A patch was published on 2026-05-25: Upstream version 1.3.3 released. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41048 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-41048?
- 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 vulnerability exists in the qSnapper D-Bus daemon (qsnapper-dbus-service) due to the incorrect implementation of an internal authentication cache. The daemon used a shared 'm_authenticated' flag that, once set by a successful Polkit authorization, would bypass subsequent checks for different actions. For example, a user authorized for the 'delete-snapshot' action would implicitly gain authorization for 'rollback-snapshot' because the flag remained set. Additionally, because the flag was shared across the service instance, one user's successful authentication could allow other unprivileged users (including 'nobody') to execute protected D-Bus methods. This has been fixed in version 1.3.3 by removing the internal cache and relying on Polkit's native 'auth_admin_keep' behavior.
Affected products
- presire qSnapper >= 1.2.1, < 1.3.3
Timeline
- 2026-04-16: disclosed: Vulnerability identified during SUSE security review.
- 2026-05-25: patched: Upstream version 1.3.3 released.
- 2026-06-22: advisory: NVD publication date.