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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A path traversal vulnerability in qsnapper via the `config` parameter.
A path traversal vulnerability in qSnapper D-Bus methods that accept configName, allowing arbitrary configuration files to be supplied to libsnapper and enabling arbitrary file write, DoS, and information leak scenarios; combined with the Polkit bypass it can lead to full local root compromise.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.