Skip to main content
Mallory
MediumVulnerability

CVE-2026-41047: Information disclosure in qSnapper snapshot diff functions

Published Jun 22, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.9Medium · v4
EPSS0.20%10th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
presire
IdentifiersCVE-2026-41047CWE-862

qSnapper before 1.3.3 exposed multiple snapshot diff-related D-Bus methods under the weaker list-snapshots Polkit action, which was allowed for locally logged-in users without authentication. As a result, local users could invoke methods including ListSnapshots(), GetFileChanges(), GetFileDiffAndDetails(), GetFileChangesBetween(), and GetFileDiffBetween() against snapshots managed by the privileged qsnapper-dbus-service running as root. These methods disclosed metadata changes for arbitrary files between snapshots or between a snapshot and the live filesystem, and GetFileDiffBetween() could return full file-content diffs. This created a local information disclosure vulnerability that allowed access to otherwise read-protected information, including sensitive files such as /etc/shadow or files in root’s home directory.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a locally logged-in unprivileged user to obtain sensitive information from snapshot contents and filesystem change history without the intended authentication. Depending on the target files present in snapshots, the attacker can learn metadata changes, file existence and modification details, and in some cases recover full diff output for protected file contents. This can expose secrets and system state that would normally require elevated privileges to read.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict local access to systems running qSnapper, review and harden the Polkit policy so diff-related operations require administrative authentication, and limit or disable access to the privileged qSnapper D-Bus service for untrusted local users where operationally feasible. Reducing exposure of sensitive snapshots and restricting interactive local logins also lowers risk.

Remediation

Patch, then assume compromise.

Upgrade qSnapper to version 1.3.3 or later. The fix introduced a dedicated view-diff Polkit action protected with auth_admin, separating diff access from the less-privileged snapshot-listing capability.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
presireQsnapperapplication
FAQ

Frequently asked questions

Is CVE-2026-41047 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-41047 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-41047?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-41047.
Is there a patch for CVE-2026-41047?
Upgrade qSnapper to version 1.3.3 or later. The fix introduced a dedicated view-diff Polkit action protected with auth_admin, separating diff access from the less-privileged snapshot-listing capability.
What products are affected by CVE-2026-41047?
presire Qsnapper.
How severe is CVE-2026-41047?
CVE-2026-41047 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 0.20% (10th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.