/

CVE-2026-41477

Severity:

HIGH RISK

(7.8)

Missing Authentication for Critical Functionality

CVE-2026-41477

Analyzed

Vulnerability type

Category:

Missing Authentication for Critical Functionality

CWE:

CWE-306, CWE-862

Impact:

Local Privilege Escalation to SYSTEM

Severity:

HIGH RISK

(7.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Deskflow's daemon component exposes a named pipe with world-access permissions and processes privileged commands without any authentication.

On affected versions, any local unprivileged user who can reach this IPC endpoint may execute arbitrary commands with SYSTEM-level privileges.

Affected context

This vulnerability exists in the Deskflow daemon, which runs as SYSTEM on Windows and exposes an IPC named pipe with WorldAccessOption enabled.

It becomes relevant on systems where:

  • Deskflow (stable 1.20.0+ or Continuous 1.26.0.134 prerelease and earlier) is installed and running
  • The daemon process listens on a globally accessible named pipe
  • Unprivileged local users can establish connections to that pipe from the same host

In such environments, the daemon interprets and executes commands received over the pipe as privileged operations, without verifying the caller's identity or authorization level.

Exploit preconditions

  • Attack surface: Local inter-process communication (IPC) via Windows named pipe
  • Required access: Any local account or code running on the same machine that can open the named pipe
  • Trigger point: Sending crafted control messages or commands over the exposed named pipe to the Deskflow daemon
  • Why exploitation is possible:
  • The named pipe is created with WorldAccessOption, making it broadly accessible
  • The daemon runs as SYSTEM and trusts all requests arriving via the pipe
  • There is no authentication, authorization, or caller identity validation before executing privileged commands

Why this happens

The core issue is that the Deskflow daemon exposes critical administrative functionality over an IPC channel without enforcing authentication or authorization.

By creating the named pipe with permissive world-access permissions and treating all incoming requests as trusted, the daemon effectively grants SYSTEM-level capabilities to any local user who can connect.

This maps to:

  • CWE-306: Missing Authentication for Critical Function — the daemon fails to verify that the caller is authorized before performing privileged actions.
  • CWE-862: Missing Authorization — there is no access control check to differentiate between privileged and unprivileged callers.

Architecturally, the design incorrectly assumes that being on the same host and reaching the named pipe is equivalent to being trusted, violating the principle of least privilege.

Potential impact

  • Local users may gain SYSTEM-level code execution on the affected machine
  • Attackers could install persistent malware or backdoors with full system privileges
  • Security controls relying on user privilege separation can be bypassed
  • Sensitive system settings and files could be modified or destroyed
  • Other users' data on the system could be accessed or exfiltrated

General mitigation guidance

Effective mitigation typically involves tightening both IPC exposure and privilege boundaries:

  • Restrict access to the named pipe to only trusted service accounts or administrators, using strict ACLs rather than world-access options
  • Introduce explicit authentication on the IPC channel, such as verifying the caller's security context before processing commands
  • Implement fine-grained authorization checks for each privileged operation, ensuring only specific identities can invoke them
  • Reduce the daemon's runtime privileges where possible, avoiding SYSTEM unless strictly necessary
  • Apply defense-in-depth measures such as isolating service components, sandboxing helper processes, and enforcing least privilege across the application's architecture

How teams detect issues like this

To detect this class of issue, organizations can:

  • Review service and daemon code for:
  • IPC endpoints (named pipes, sockets) that handle privileged operations
  • Absence of authentication or authorization checks before executing sensitive actions
  • Use static analysis or security linters to flag:
  • Creation of globally accessible named pipes or IPC objects
  • Direct execution of commands or elevated actions triggered by unvalidated IPC requests
  • Perform configuration and deployment audits to:
  • Identify services running as SYSTEM or equivalent high-privilege accounts
  • Inspect ACLs on IPC endpoints and ensure they are not world-accessible by default
  • Include security-focused code reviews where reviewers explicitly trace:
  • The flow from external endpoints (like IPC) to privileged routines
  • Any assumptions about trust based solely on local machine access

Sources

SourceLink
github.comgithub.com/deskflow/deskflow/security/advisories/GHSA-6rx5-g478-775c

Frequently asked

questions

It is primarily a local privilege escalation issue. An attacker must already have local code execution or a user account on the machine to access the named pipe. However, remote compromise of a low-privilege account (e.g., via phishing or another vulnerability) could be chained with this weakness to gain SYSTEM privileges.

The attacker needs only local, unprivileged access sufficient to open the Deskflow named pipe. No administrative rights or prior elevation are required; the vulnerable daemon provides the privilege escalation by executing commands as SYSTEM.

The safest pattern is to enforce strict authentication and authorization for any IPC channel that controls privileged functionality. Combine this with restrictive ACLs on IPC endpoints and minimize the use of high-privilege service accounts. Critical commands should only be accepted from authenticated, explicitly authorized principals.

Prevention strategies include designing IPC interfaces under a "zero trust" model, where local reachability does not imply trust. Always validate the caller's identity and enforce fine-grained authorization, adopt least-privilege service configurations, and incorporate security reviews and automated checks focused on service boundaries and access control before release.

Find out what's already
exploitable in your codebase.