CVE-2026-10696: UniGetUI WinGet Backend Package Name Mismatch RCE

Technical summary

The vulnerability exists in UniGetUI's pinget backend name resolution logic. When processing update candidates, the system fails to properly disambiguate between installed applications and catalog packages, relying instead on substring matching of normalized package names. An attacker with WinGet community catalog contributor privileges can exploit this by creating a crafted package whose normalized name appears as a substring within a legitimate installed application's name. Upon user-initiated update, the backend incorrectly correlates the installed app to the attacker's catalog entry and executes the attacker-controlled installer. The flaw is rooted in insufficient validation of package identity correlation (CWE-706: Use of Incorrectly Resolved Name or Reference).

Business impact

This vulnerability allows supply-chain attacks through the WinGet community package ecosystem. Users running affected UniGetUI versions who attempt to update applications are at risk of silent installer substitution, potentially leading to installation of malware, backdoors, or other unauthorized software. The attack requires no user interaction beyond the normal update workflow, making it especially dangerous in environments where users regularly patch their systems. Organizations relying on UniGetUI for application lifecycle management should assess their exposure and update procedures.

Affected systems

Devolutions UniGetUI version 2026.2.0 and earlier are vulnerable. The attack surface is limited to users who: (1) use UniGetUI as their package manager frontend, (2) have applications installed whose names could be targeted by substring matching, and (3) initiate update checks through the affected backend. The WinGet community catalog must be enabled for exploitation.

Exploitability

Exploitation requires an attacker to be an accepted WinGet community catalog contributor. While this represents a gating factor, the WinGet community model is designed to be relatively open to legitimate contributors, potentially lowering the bar for malicious actors to gain access. Once a malicious package is published, exploitation is automatic upon user update; no additional user interaction or social engineering is needed beyond standard update behavior.

Remediation

Update Devolutions UniGetUI to a patched version released after 2026.2.0. Verify the availability of patches through the official Devolutions website or UniGetUI update mechanism. Until patching is possible, consider temporarily disabling automatic update checks or restricting WinGet community catalog access if your organization controls that setting.

Patch guidance

Devolutions has released patches post-2026.2.0 to address the name resolution flaw. Users should update UniGetUI through the application's built-in update feature or by downloading the latest release from the official Devolutions repository. Verify against vendor advisories to confirm the patched version resolves CWE-706 in the pinget backend. No intermediate mitigations are available short of upgrading.

Detection guidance

Monitor for unusual installer execution patterns triggered by UniGetUI update operations. Log package manager backend activity if possible, paying attention to cases where the package name associated with an update differs significantly from the application being updated. Security tools should flag unexpected executable downloads or execution from UniGetUI's cache directories. Threat intelligence feeds tracking WinGet community catalog abuse may provide early warning of published malicious packages.

Why prioritize this

This is a HIGH severity vulnerability (CVSS 7.5) because it combines high availability impact with a practical attack vector that requires only network access and prior repository access, not local system compromise. The fact that exploitation is automatic during normal update workflows and can affect any user in an organization makes it a strong candidate for rapid patching. Organizations managing large application inventories via UniGetUI should prioritize this immediately.

Risk score, explained

The CVSS 3.1 score of 7.5 (HIGH) reflects: (1) Network-accessible attack vector requiring no special conditions (AV:N/AC:L); (2) No special privileges required to exploit (PR:N); (3) No user interaction beyond routine update actions (UI:N); (4) Availability impact due to potential system compromise via arbitrary installer execution (A:H). The score does not capture confidentiality or integrity in the vector, but the ability to execute arbitrary code clearly poses both risks. This score appropriately emphasizes the threat level.

Frequently asked questions