HIGH 7.1

CVE-2026-41049: qSnapper D-Bus Authentication Caching Privilege Escalation

A flaw in the qSnapper D-Bus service allows unprivileged local users to hijack authenticated sessions. When a privileged user authenticates to perform an action via D-Bus, the service incorrectly caches that authentication state without proper isolation. A local attacker can then invoke the same D-Bus functions without re-authenticating, effectively using the elevated privileges that were granted to the legitimate user. This is a local privilege escalation vulnerability requiring an existing login session on the affected system.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.1 HIGH · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Weaknesses (CWE)
CWE-863
Affected products
1 configuration(s)
Published / Modified
2026-06-22 / 2026-07-08

NVD description (verbatim)

Incorrect caching of authentication between different users of the  qSnapper dbus service before version 1.3.3 allowed any local attacker to use dbus functions after a privileged users has authenticated for them.

3 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-41049 stems from improper authentication caching in the qSnapper D-Bus service (presire qSnapper before version 1.3.3). The vulnerability is classified under CWE-863 (Incorrect Authorization). The D-Bus mechanism fails to bind cached authentication credentials to the requesting user context, instead storing them globally or without sufficient scope isolation. When a privileged user authenticates to execute a D-Bus method, subsequent unauthenticated requests from a different local user are processed using the cached credentials from the first user's session. An attacker with local system access can exploit this race condition or session-reuse window to invoke privileged operations without providing valid credentials.

Business impact

Organizations relying on qSnapper for administrative or privileged operations face a serious elevation-of-privilege risk. Any unprivileged local user—including service accounts, container processes, or compromised standard user accounts—can potentially perform administrative tasks intended only for privileged administrators. In multi-tenant or shared-system environments, this could lead to unauthorized configuration changes, data exfiltration, system compromise, or lateral movement. The impact extends beyond confidentiality to include integrity violations and availability degradation, making this a high-priority remediation issue for systems managing sensitive operations.

Affected systems

presire qSnapper versions prior to 1.3.3 are affected. Any system running a vulnerable version with D-Bus enabled and relying on qSnapper for privilege-separated operations is at risk. This includes Linux-based systems using qSnapper for snapshot or administrative management. The vulnerability requires local access, so it primarily impacts multi-user systems, shared hosting environments, and systems where untrusted local processes operate alongside privileged services.

Exploitability

This vulnerability has a low barrier to exploitation for local attackers. It requires only local system access (no remote network exploitation) and no user interaction beyond timing the invocation after a privileged user has authenticated. The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U) reflects this: attackers need a valid local account (PR:L) but face low complexity (AC:L) and no interaction requirement (UI:N). The vulnerability is not currently tracked in the CISA Known Exploited Vulnerabilities catalog, but the straightforward nature of session-cache exploitation makes it likely to be weaponized once public details surface. No exploit proof-of-concept should be assumed as unavailable.

Remediation

Organizations must upgrade presire qSnapper to version 1.3.3 or later. The fix addresses the authentication caching mechanism to ensure credentials are properly isolated per-user and session, preventing cross-user reuse. Before patching, consider restricting D-Bus service access via firewall rules or AppArmor/SELinux policies to limit which local users can invoke qSnapper operations. Verify the patch version against the vendor advisory prior to deployment.

Patch guidance

Upgrade presire qSnapper to version 1.3.3 or later. Consult the presire security advisory and release notes to confirm the patch version and any prerequisite configuration changes. Test the upgrade in a non-production environment to ensure compatibility with existing D-Bus policies and dependent applications. If upgrading is delayed, apply compensating controls: restrict D-Bus service activation permissions using system policies, disable qSnapper if not actively required, and monitor D-Bus method calls for anomalous cross-user invocations.

Detection guidance

Monitor D-Bus activity for suspicious patterns: multiple method invocations from low-privilege users immediately following high-privilege authentication events, or repeated calls to privileged qSnapper functions from unprivileged user contexts. Enable D-Bus audit logging (via systemd-journald or auditd) to capture service activation and method calls. Check for unauthorized privilege escalation attempts in syslog. In container environments, monitor for unexpected qSnapper operations from non-admin processes. Baseline normal D-Bus usage patterns and alert on deviations that suggest session-cache reuse.

Why prioritize this

This vulnerability merits HIGH priority remediation due to the combination of local privilege escalation (CWE-863), HIGH CVSS score (7.1), and low exploitation complexity. While it requires local access, the lack of authentication re-validation and the multi-user attack surface make it a practical exploitation vector in many organizations. Environments with shared systems, container orchestration, or service-account interactions should treat this as urgent.

Risk score, explained

The CVSS 3.1 score of 7.1 (HIGH) reflects: (1) local attack vector with no network exposure, (2) low attack complexity due to straightforward D-Bus mechanism abuse, (3) low privilege requirement (only a standard user account needed), (4) no user interaction, (5) high integrity impact (unauthorized privilege execution), and (6) high availability impact (potential system disruption via misuse of privileged functions). The unscoped impact (S:U) means the attacker's privileges affect only their own D-Bus session context, limiting but not eliminating damage.

Frequently asked questions

Can this vulnerability be exploited remotely?

No. CVE-2026-41049 requires local system access. Remote attackers cannot exploit this without first gaining a local login session or compromised process on the affected system.

Do I need to restart services or the system after patching qSnapper?

Verify the specific upgrade guidance in the presire security advisory. Typically, restarting the qSnapper service (and any dependent services) and restarting any D-Bus sessions will ensure the fix is applied. A full system restart is often the safest approach but may not always be necessary.

What if I can't upgrade immediately?

Apply compensating controls: restrict D-Bus access via systemd security policies or SELinux/AppArmor, disable qSnapper if not in active use, and monitor D-Bus logs for signs of exploitation. However, patching should remain the primary remediation path.

Is this vulnerability being actively exploited in the wild?

As of the publication date, this vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog. However, the low complexity of exploitation means organizations should not assume it remains unused by threat actors. Prioritize patching accordingly.

This analysis is provided for informational purposes and reflects the vulnerability details as published. Organizations must verify all patch versions, compatibility notes, and vendor guidance directly against presire's official security advisories before deploying updates. Testing in non-production environments is strongly recommended. SEC.co makes no warranty regarding the completeness or real-time accuracy of this intelligence and recommends consulting vendor documentation and security bulletins for the most current information. Source: NVD (public-domain), retrieved 2026-07-28. Analysis generated by SEC.co (claude-haiku-4-5).