🛡️ CVE-2026-41049 — qsnapper

🟠 CVSS 7.1 — High ✅ No Known Exploit CWE-863 NVD
7.1
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Incorrect caching of authentication between different users of the  qSnapper dbus service before version 1.3.3 allowed any local attacker to use dbus functions after a privileged users has authenticated for them.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity high, availability high.

Weakness class

CVE-2026-41049 is classified as CWE-863: Incorrect Authorization. An authorisation check runs but reaches the wrong conclusion, permitting actions it should refuse.

Affected software

CVE-2026-41049 is recorded against 1 package.

  • qsnapper (fixed in 1.3.3)

Timeline and source

Published on 22 June 2026 and last revised on 8 July 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

bugzilla.suse.com
github.com
security.opensuse.org

Details

Severity HIGH
CVSS Score 7.1
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
CWE CWE-863
Public Exploit ✅ No
Source NVD
Published 2026-06-22
Updated 2026-08-11
Modified 2026-07-08
Fix URL N/A

Affected Packages

Software From version Fixed in
qsnapper — 1.3.3

Similar Threats

Site Security Check

Is qsnapper part of your stack?

CVE-2026-41049 is rated CVSS 7.1 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.