qSnapper: Relative Path Traversal
CVE-2026-41046 is a high-severity relative path traversal vulnerability in qSnapper from Presire, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 1.3.3 as the first without the flaw, so updating qSnapper to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.18% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update qSnapper to 1.3.3 or a later version.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.3 | High | CNA (suse.de) |
| CVSS 3.1 | 7.3 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Relative Path Traversal
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as.. that can resolve to a location that is outside of that directory.
How developers prevent this class of flaw
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/presire/qSnapper/releases/tag/v1.3.3Release Notes
Third-party and government advisories
- bugzilla.suse.com/show_bug.cgi?id=1261889Third Party Advisory
- security.opensuse.org/2026/05/26/qsnapper-dbus-issues.html#issue-path-traversalThird Party Advisory, Issue Tracking
Other vulnerabilities in qSnapper
- 7.1 High severity
- 7.1 High severity
- 7.0 High severity
Recent Relative Path Traversal vulnerabilities
- 8.6 High severity
- 7.1 High severity
- 8.1 High severity
- 7.5 High severity
- 10.0 Critical severity
- 7.8 High severity
Spotted an error? Tell us.