Local service interruption via unchecked configuration paths
Published Jun 22, 2026 · Updated Jun 22, 2026
Relative path traversal in qSnapper before 1.3.3 allows local users to hang or crash its privileged D-Bus service via configName. All D-Bus methods pass configName directly to libsnapper as a basename without rejecting slashes or dot-dot components, so crafted paths select arbitrary configuration files. Locally logged-in users can reach list-snapshots methods without authentication, causing memory exhaustion or blocking; arbitrary writes and root escalation require admin access or a separate Polkit bypass.
Summary
What happened
Relative path traversal in qSnapper before 1.3.3 allows local users to hang or crash its privileged D-Bus service via configName. All D-Bus methods pass configName directly to libsnapper as a basename without rejecting slashes or dot-dot components, so crafted paths select arbitrary configuration files. Locally logged-in users can reach list-snapshots methods without authentication, causing memory exhaustion or blocking; arbitrary writes and root escalation require admin access or a separate Polkit bypass.
The record
- CVE
- CVE-2026-41046
- Published
- Jun 22, 2026
- Updated
- Jun 22, 2026
- Vendor
- presire
- Product
- qSnapper
- Classifications
- CWE-23, CAPEC-17, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 2026CVE publishedPublication date reported by the CVE source.
- Jun 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.3.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo