Skip to main content

qSnapper CVE-2026-41046

| EUVDEUVD-2026-38263 HIGH
Relative Path Traversal (CWE-23)
2026-06-22 suse GHSA-3hfq-9fxf-h35p
7.3
CVSS 3.1 · NVD
Share

Severity by source

Vendor (suse) PRIMARY
HIGH
qualitative
NVD
7.3 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
vuln.today AI
6.6 MEDIUM

Local D-Bus access requires an unprivileged local account so PR:L (not PR:N); low complexity, no UI; high availability from DoS, low C/I from config-driven side effects short of confirmed full RCE.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative

Primary rating from Vendor (suse).

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
High

Lifecycle Timeline

3
Patch available
Jun 22, 2026 - 17:01 EUVD
Source Code Evidence Fetched
Jun 22, 2026 - 16:04 vuln.today
Analysis Generated
Jun 22, 2026 - 16:04 vuln.today

DescriptionNVD

A path traversal attack when using a "configName" parameter in qSnapper before version 1.3.3 allowed a local attacker to use malicious config files for snapper and so cause a denial of service or potentially escalate privileges to root.

AnalysisAI

Local privilege escalation and denial of service in qSnapper before 1.3.3 stems from path traversal via the configName D-Bus parameter, allowing local attackers to point the snapper backend at attacker-controlled config files. Per the SUSE security review that produced coordinated fixes for CVE-2026-41045 through CVE-2026-41049, exploitation can crash the service or escalate to root through abuse of snapper configuration handling. No public exploit identified at time of analysis, but the upstream advisory and Bugzilla entry document the issue in detail.

Technical ContextAI

qSnapper is a Qt-based front-end and D-Bus service for snapper, the Btrfs/ext4 snapshot management tool widely used on openSUSE/SLES. The vulnerability is a CWE-23 relative path traversal in the configName argument accepted by multiple D-Bus methods: the service did not constrain the value to a snapper config identifier, so '..' sequences and unexpected characters allowed selecting arbitrary files as a snapper config. Because qSnapper's privileged D-Bus methods ultimately invoke snapper as root, controlling the config path translates into root-level file/process behavior. The 1.3.3 release introduces validateConfigName() enforcing the allowlist regex ^[A-Za-z0-9_.-]+$ at every D-Bus entry point accepting configName.

RemediationAI

Vendor-released patch: qSnapper 1.3.3 - upgrade immediately via the project release at https://github.com/presire/qSnapper/releases/tag/v1.3.3 or the distribution package once published per SUSE Bugzilla 1261889. The 1.3.3 fix adds validateConfigName() with an ^[A-Za-z0-9_.-]+$ allowlist applied at every D-Bus method that accepts configName and is bundled with related D-Bus hardening (CVE-2026-41045/47/48/49) that should be taken together. If upgrading is not immediately possible, restrict access to the com.presire.qsnapper D-Bus service by tightening the D-Bus policy file so only trusted administrative users can invoke its methods, or stop and mask the qSnapper service on multi-user systems; the trade-off is that legitimate non-admin users will lose snapshot management functionality until patched.

Vendor StatusVendor

SUSE

Severity: Important

Share

CVE-2026-41046 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy