CVE-2026-112174Enter Iperius Backup unnecessary privileges
CVE-2026-112174 is a unnecessary privileges in Enter Iperius Backup, rated critical (9.3 on CVSS 4.0).
Why this priority: Critical severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
The software runs with more privileges than it needs, so any flaw in it is worse.
How it is reached
An attacker can exploit it by someone who can already run code or sign in on the machine, with an ordinary user account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker reach data or actions their role should not allow. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place Enter Iperius Backup runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- Limit who can run code or sign in on the hosts that run it.
Description from NVD
Local privilege escalation vulnerability in Iperius Backup 8.8.3, due to insufficient separation between the graphical user interface running with elevated privileges and local users with low privileges. When the backup service is configured to run persistently with Administrator privileges, a local attacker with low privileges can use the native Windows dialogues exposed by the application to run programmes that inherit its elevated context. This allows commands to be executed with SYSTEM or Administrator privileges, depending on the application’s context, and compromises the affected Windows system.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Permission checks in APIs and admin surfaces. The flaw sits between one role or tenant and another.
- Multi-tenant services. The flaw sits between one role or tenant and another.
Trust boundaries in play
- Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between one role or tenant and another. An attacker who crosses it can reach data or actions their role should not allow.
Questions to answer about your own systems
- Where does Enter Iperius Backup run in your systems, and at which version?
- Which of those hosts also run code or users you do not fully trust?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.