CVE-2026-41047
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 · uneditedLack of authentication when using the "snapshot diff" functions in qSnapper before version 1.3.3 allowed a local attacker to see otherwise read protected information.
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 · high confidenceqSnapper before version 1.3.3 lacks authentication checks in its 'snapshot diff' functions, allowing a local attacker to access read-protected snapshot information without credentials. This is an authorization bypass vulnerability where the diff feature bypasses access controls.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 executables or installation directories on the system. Common paths include /usr/bin/qsnapper, /opt/qsnapper/, or check installed packages via system package manager (dpkg -l | grep qsnapper, rpm -qa | grep qsnapper)Affected if qSnapper is not found on the system, so the vulnerability does not apply
-
Determine installed versionRun qsnapper --version or check the package version via system package manager (dpkg -l qsnapper or rpm -qi qsnapper) to retrieve the exact version numberAffected if Installed version is lower than 1.3.3 (for example, 1.3.2, 1.3.0, 1.2.x, etc.)
-
Verify snapshot diff functionality existsCheck if the snapshot diff command or feature is available by running qsnapper --help or looking for diff-related subcommands in the qSnapper binaryAffected if The snapshot diff feature exists and is accessible to the user without authentication credentials
User is affected if qSnapper is installed with version lower than 1.3.3 and the snapshot diff feature is accessible without credentials.
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 implements proper authentication on snapshot diff functions. Until patched, limit local access to systems running qSnapper.
1.3.3
- Update your package manager repository metadata
- Install qSnapper version 1.3.3 or later via your system's package manager (e.g., zypper for openSUSE/SUSE or dnf for Fedora/RHEL-based systems)
- Verify the installed version matches or exceeds 1.3.3 using: qsnapper --version or rpm -q qsnapper
- Test that the snapshot diff functionality now properly requires authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41047 — 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-41047 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