/

CVE-2026-41046

Severity:

HIGH RISK

(7.3)

Path Traversal (CWE-23) in qSnapper Config Handling

CVE-2026-41046

Analyzed

Vulnerability type

Category:

Path Traversal

CWE:

CWE-23

Impact:

Local Privilege Escalation and Denial of Service

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A path traversal flaw in qSnapper's handling of the configName parameter allows a local attacker to reference malicious Snapper configuration files outside the intended directory.

When exploited, this can lead to denial of service or, under certain configurations, escalation of privileges up to root.

Affected context

The vulnerability appears in qSnapper deployments that pass user-supplied or otherwise untrusted values into the configName parameter without constraining them to a fixed configuration directory.

It is most relevant in environments where qSnapper interacts with Snapper configurations that may be executed or interpreted with elevated privileges.

The issue is local in nature, relying on filesystem access and the ability to influence which configuration file qSnapper uses.

Exploit preconditions

  • Attack surface: Local system interface where configName can be influenced (GUI, CLI wrapper, or configuration file).
  • Required access: Local user access on the host where qSnapper runs; the attacker must be able to invoke qSnapper or affect its parameters.
  • Trigger point: Supplying a crafted configName value that uses directory traversal sequences (e.g., ../) or absolute paths to select an attacker-controlled Snapper configuration.
  • Why exploitation is possible: The application does not adequately normalize and validate the configName parameter against an allowlisted set of configuration names or a fixed root directory, allowing traversal outside the intended configuration location.

Why this happens

This vulnerability stems from improper validation of file paths derived from user-influenced input, aligning with CWE-23: Relative Path Traversal.

Instead of mapping a logical configuration name to a safe, canonical path, qSnapper appears to concatenate or otherwise directly reuse the configName value when determining which Snapper configuration file to load.

Without normalization, canonicalization, and strict restriction to an expected directory or whitelist, path traversal sequences allow access to unintended configuration files, some of which may be processed with higher privileges.

Potential impact

  • qSnapper or Snapper may load a malicious configuration and become unusable, causing denial of service.
  • System snapshot management may be disrupted, impacting backup and rollback operations.
  • An attacker could influence privileged operations performed via Snapper, potentially escalating privileges to root.
  • Misconfigured or hostile configurations could lead to data loss or inconsistent system states.

General mitigation guidance

Effective mitigation focuses on strict control of how configuration names map to filesystem paths:

  • Treat configName as an opaque logical identifier and resolve it via a fixed, internal mapping to safe paths rather than concatenating it into file paths.
  • Enforce that all resolved configuration files reside under a single, predefined directory, and reject any path that escapes this root after canonicalization.
  • Apply stringent input validation and normalization, rejecting values containing directory traversal tokens, path separators, or absolute paths.
  • Drop privileges or perform configuration parsing in a less-privileged context wherever possible, minimizing the blast radius if a configuration is abused.
  • Favor secure-by-default behavior such as using a small, explicit whitelist of allowed configuration names for typical deployments.

How teams detect issues like this

Detection can rely on both code-centric and system-centric approaches:

  • Use static analysis rules to flag code paths that construct file paths directly from user-controlled or external parameters without canonicalization and directory constraints.
  • During code review, look for patterns where configuration names or identifiers are concatenated with directory strings or passed unfiltered to file APIs.
  • Implement runtime logging that records selected configuration names and their resolved paths; monitor for suspicious patterns such as traversal sequences or unexpected directories.
  • Integrate automated security linters or SAST tools into CI pipelines to detect path traversal patterns across file access code.

Sources

SourceLink
bugzilla.suse.combugzilla.suse.com/show_bug.cgi?id=1261889
github.comgithub.com/presire/qSnapper/releases/tag/v1.3.3
security.opensuse.orgsecurity.opensuse.org/2026/05/26/qsnapper-dbus-issues.html#issue-path-traversal

Frequently asked

questions

No, the issue is described as a local attack. The attacker needs local access to the system and the ability to influence the configName parameter or how qSnapper is invoked.

The attacker must have a local user account or equivalent local execution capability on the affected host. From there, they can attempt to supply crafted configuration names to qSnapper.

The safest fix is to decouple logical configuration identifiers from raw filesystem paths: use a whitelist or internal mapping of allowed configuration names to canonical paths, enforce that all paths stay within a predefined directory, and reject any input that cannot be resolved safely.

Adopt a design rule that user-influenced values are never used directly as file paths. Always perform canonicalization, enforce directory restrictions, use allowlists for configuration identifiers, and include static analysis and security-focused code reviews in the development lifecycle.

Find out what's already
exploitable in your codebase.