CVE-2026-41046
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceqSnapper before version 1.3.3 contains a path traversal vulnerability in the 'configName' parameter. An attacker can manipulate this parameter to reference arbitrary file paths, loading malicious snapper configuration files. This can cause denial of service or potentially enable privilege escalation to root by exploiting the snapper tool's privileged operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.3.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate qSnapper installationSearch for qSnapper executable or service on the system using standard package management tools or file system searches for 'qsnapper' or 'qsnap'Affected if qSnapper is found running on the system and its version is below 1.3.3
-
Determine installed versionRun 'qsnapper --version' or check the application metadata/package information to identify the exact version numberAffected if The version returned is earlier than 1.3.3 (for example, 1.3.2, 1.3.1, 1.2.x, etc.)
-
Identify how configName parameter is exposedExamine qSnapper's interface (web UI, API endpoint, or CLI) to determine if there is a 'configName' parameter used for loading snapper configurationsAffected if The configName parameter is accessible to users without proper validation and accepts arbitrary string input
-
Verify snapper configuration loading mechanismTest whether supplying a path-like value to configName (such as '../etc/passwd' or an absolute path) causes qSnapper to attempt loading that file as a configurationAffected if qSnapper accepts path traversal sequences in configName and attempts to load files outside the intended configuration directory
-
Check for privileged snapper operationsDetermine if qSnapper runs with elevated privileges or invokes snapper with root-level permissions for snapshot managementAffected if qSnapper operates with root or sudo privileges and can be manipulated via the path traversal to load malicious snapper configuration files
The environment is affected if qSnapper version is below 1.3.3 AND the configName parameter accepts user-controlled input without validation, allowing path traversal to load arbitrary snapper configuration files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.3.3
Upgrade qSnapper to version 1.3.3 or later which includes proper input validation for the configName parameter to prevent path traversal.
1.3.3
- Upgrade qSnapper to version 1.3.3 or later to remediate the path traversal vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41046 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41046 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data