HIGH 7.8

CVE-2026-57919: Matrix42 Empirum Privilege Escalation via Named Pipe DACL Weakness

A privilege escalation vulnerability exists in Matrix42 Empirum's backup component (PBackupVSS.exe). The application creates a shared communication channel (named pipe) that allows any user logged into the system to send commands to it. An attacker with a basic user account can exploit this to run commands with the highest system privileges, potentially compromising the entire machine. The attack works by placing a malicious file in a directory that the backup process searches through during normal operation.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.8 HIGH · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-276, CWE-426
Affected products
0 configuration(s)
Published / Modified
2026-06-29 / 2026-07-17

NVD description (verbatim)

PBackupVSS.exe in Matrix42 Empirum before 25.5 and 26.x before 26.2 creates a named pipe (\\.\pipe\PBackupVSS) with a DACL that grants GENERIC_READ and GENERIC_WRITE permissions to all authenticated users. A low-privileged local attacker can connect to this pipe and send crafted IPC messages to trigger execution of arbitrary commands with SYSTEM privileges via an untrusted search path. This allows privilege escalation by placing a malicious shadow.exe in a controlled working directory.

3 reference(s) · View on NVD →

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

Technical summary

CVE-2026-57919 is a local privilege escalation vulnerability in Matrix42 Empirum versions before 25.5 and 26.x before 26.2. The PBackupVSS.exe process creates a named pipe at \\.\pipe\PBackupVSS with a DACL permitting GENERIC_READ and GENERIC_WRITE access to all authenticated users (CWE-276: Incorrect Default Permissions). A low-privileged attacker can connect to this pipe and transmit specially crafted inter-process communication (IPC) messages that trigger command execution with SYSTEM context. Exploitation leverages an insecure search path (CWE-426: Untrusted Search Path) by placing a malicious shadow.exe in a controlled working directory, which the process loads and executes with elevated privileges.

Business impact

Successful exploitation allows an insider or local attacker to bypass access controls and gain full administrative control over affected systems. This enables data theft, malware installation, system manipulation, and lateral movement to other networked resources. Organizations running Empirum for backup and disaster recovery face operational disruption, data loss, and compliance violations if the system is compromised. The vulnerability is particularly concerning in environments where Empirum manages critical infrastructure or sensitive backup operations.

Affected systems

Matrix42 Empirum versions before 25.5 and all 26.x versions before 26.2 are vulnerable. Any deployment of these versions with PBackupVSS.exe running (typically as a service with SYSTEM privileges) presents an exposure. The vulnerability requires local system access; remote exploitation is not possible. Systems with multi-user access, shared workstations, or containers running Empirum are at higher risk.

Exploitability

Exploitation requires local access and low privileges—realistic for disgruntled employees, contractors, or attackers who have compromised a user account. No special tools or advanced techniques are required; a standard user account and the ability to write files to a directory that the backup process searches constitute sufficient capability. The CVSS 3.1 score of 7.8 (HIGH) reflects these conditions: low attack complexity, no user interaction needed, and complete impact across confidentiality, integrity, and availability.

Remediation

Upgrade Matrix42 Empirum to version 25.5 or later for the 25.x branch, or to version 26.2 or later for the 26.x branch. Organizations unable to patch immediately should restrict local system access to trusted users only, use OS-level privilege separation where available, and monitor named pipe access for suspicious activity. Verify that PBackupVSS.exe is running with minimal necessary privileges and confirm that shadow.exe and other dependent binaries are loaded from secure, protected directories only.

Patch guidance

Consult the Matrix42 advisory for exact patched versions and deployment steps. Generally, update to 25.5+ or 26.2+, test the upgrade in a non-production environment first, and ensure backup processes remain functional after patching. Coordinate with backup and disaster recovery teams to minimize downtime. Verify that the named pipe permissions and search path behavior have been corrected post-patch.

Detection guidance

Monitor for unexpected connections to the \\.\pipe\PBackupVSS named pipe from unprivileged processes. Log and alert on creation or execution of shadow.exe outside of trusted Matrix42 installation directories. Review access control lists (ACLs) on the named pipe to confirm they have been restricted. Audit file system activity in directories that might be used as working directories for PBackupVSS.exe. Implement application whitelisting to prevent unauthorized execution of backup-related binaries.

Why prioritize this

Although KEV listing status does not currently flag this vulnerability and exploit code is not yet weaponized, the combination of local access, low complexity, and complete system compromise makes this HIGH priority. Any environment where non-administrative users share system access or where Empirum runs services accessible from compromised user accounts should patch urgently. Organizations relying on Empirum for backup integrity should treat this as critical to remediate.

Risk score, explained

The CVSS 3.1 score of 7.8 is justified by: (1) low attack complexity and low privilege requirements (exploitable by any authenticated user), (2) no user interaction required, (3) complete confidentiality, integrity, and availability impact once exploited, and (4) scope unchanged (impact limited to the single affected asset, though that asset is a high-value backup system). The score does not account for the insider threat context or the critical nature of backup systems in many environments, both of which should elevate organizational risk perception.

Frequently asked questions

Can an attacker exploit this remotely?

No. This vulnerability requires local system access and a valid user account on the affected machine. Remote exploitation is not possible.

What does patching involve, and will it disrupt backups?

Patching requires upgrading to the fixed versions (25.5+ or 26.2+). Coordinate the upgrade with your backup schedule and test thoroughly in staging first. The patch corrects the named pipe permissions and search path behavior; backup operations should continue normally once deployed.

Our environment is highly controlled—do we still need to patch?

Yes. Even in tightly controlled environments, insider threats and credential compromise remain realistic risks. Patching removes the attack vector entirely and is a baseline security practice for high-value systems like Empirum.

How can we tell if we've been exploited already?

Review Windows event logs for unexpected process execution with SYSTEM context, monitor for unusual file creation in working directories, and audit any shadow.exe instances outside the official Empirum installation folder. Consider engaging incident response if suspicious activity is detected.

This analysis is provided for informational purposes to assist security professionals in understanding and remediating CVE-2026-57919. It is not a substitute for official vendor advisories or patches. Verify all patch versions, compatibility, and deployment steps against Matrix42's official security documentation. Consult with your vendor and internal teams before applying patches to production systems. SEC.co makes no warranty regarding the completeness or accuracy of this content as it relates to your specific infrastructure. Source: NVD (public-domain), retrieved 2026-08-08. Analysis generated by SEC.co (claude-haiku-4-5).