Devolutions UniGetUI up to 2026.2.1 Pinget Backend name resolution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.87 |
Summary
A vulnerability was found in Devolutions UniGetUI up to 2026.2.1. It has been rated as critical. Impacted is an unknown function of the component Pinget Backend. The manipulation leads to name resolution. This vulnerability is listed as CVE-2026-10696. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Devolutions UniGetUI up to 2026.2.1. It has been rated as critical. This issue affects an unknown function of the component Pinget Backend. The manipulation with an unknown input leads to a name resolution vulnerability. Using CWE to declare the problem leads to CWE-706. The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Use of an incorrectly resolved name or reference in the pinget backend in Devolutions UniGetUI 2026.2.0 and earlier allows a WinGet community catalog contributor to cause an installed application to be correlated to an unrelated, attacker-controlled catalog package and to execute an attacker-controlled installer via a crafted catalog package whose normalized name is contained as a substring within the installed application name when a user applies the proposed update.
The advisory is shared at devolutions.net. The identification of this vulnerability is CVE-2026-10696 since 06/02/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/18/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-37781). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Name resolutionCWE: CWE-706
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/02/2026 CVE reserved06/17/2026 Advisory disclosed
06/17/2026 VulDB entry created
06/18/2026 VulDB entry last update
Sources
Advisory: DEVO-2026-0019Status: Confirmed
CVE: CVE-2026-10696 (🔒)
GCVE (CVE): GCVE-0-2026-10696
GCVE (VulDB): GCVE-100-372113
EUVD: 🔒
Entry
Created: 06/17/2026 21:58Updated: 06/18/2026 00:14
Changes: 06/17/2026 21:58 (53), 06/18/2026 00:14 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.