Skip to main content
Mallory
HighVulnerability

CVE-2026-41046: Path Traversal in qSnapper configName Parameter

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.
CVSS7.3High · v3.1
EPSS0.18%8th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
presire
IdentifiersCVE-2026-41046CWE-22

CVE-2026-41046 is a local path traversal vulnerability in qSnapper before version 1.3.3. The flaw affects D-Bus methods that accept the configName parameter and pass it to libsnapper without sufficient validation. By supplying traversal sequences, a local attacker can cause qSnapper’s privileged root D-Bus service to load attacker-chosen configuration files instead of restricting access to the intended Snapper configuration directory. Because the service runs with root privileges, this can be used to direct libsnapper to parse crafted configuration content, special files, or other unintended filesystem targets. The issue also affects the WriteSnapperConfig method, which can be abused through the same traversal weakness to write largely attacker-controlled configuration data to unintended locations. The vulnerability can result in denial of service, information disclosure, and in some exploit chains contribute to local privilege escalation to root.

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 local attacker to influence how the privileged qSnapper service interacts with Snapper configuration files. Documented impacts include denial of service by forcing libsnapper to process unsuitable filesystem objects, information disclosure through parsing of sensitive files as configuration input, and arbitrary file write behavior through WriteSnapperConfig to attacker-selected locations. On its own, the issue enables significant local abuse of the root-running service; when chained with the separate Polkit authentication bypass affecting qSnapper, it can contribute to full local root compromise.

Mitigation

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

If immediate patching is not possible, restrict local access to the qSnapper D-Bus interface to trusted users only, minimize or disable use of the privileged qSnapper service where operationally feasible, and review Polkit rules to reduce exposure of administrative methods. Monitoring for abnormal qSnapper configuration access and limiting availability of the service on systems where untrusted local users have accounts can reduce risk, but these measures do not fully eliminate the vulnerability because the flaw is in privileged path handling.

Remediation

Patch, then assume compromise.

Upgrade qSnapper to version 1.3.3 or later. The fix validates the configName parameter so that only intended Snapper configuration names are accepted and traversal outside the expected configuration directory is blocked. Any downstream backport should ensure all D-Bus methods accepting configName enforce strict canonicalization and allowlisting of valid configuration identifiers before invoking libsnapper or performing configuration writes.

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-41046 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-41046 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-41046?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-41046.
Is there a patch for CVE-2026-41046?
Upgrade qSnapper to version 1.3.3 or later. The fix validates the configName parameter so that only intended Snapper configuration names are accepted and traversal outside the expected configuration directory is blocked.
What products are affected by CVE-2026-41046?
presire Qsnapper.
How severe is CVE-2026-41046?
CVE-2026-41046 has a CVSS v3.1 score of 7.3 (High) and an EPSS score of 0.18% (8th 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.