VulnerabilityPublished 25 Mar 2026

CVE-2026-4823: Enter Software Iperius Backup · Information Disclosure

Affects Enter Software Iperius BackupSource CVE Database V5

Compare

Public exploit available · CVSS 2.0 Low · fixed in 8.7.4 : patch Enter Software Iperius Backup as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

2.0Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.7.4

CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: High
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Enter SoftwareIperius Backup	Affected 8.7.0 – 8.7.3 4 affected builds	Fixed in–
GitHub0truust/iperius-backup`pkg:github/0truust/iperius-backup`Other threats	Affected 8.7.0 – 8.7.3 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-4823, organizations should immediately upgrade Iperius Backup to version 8.7.4 or later, as this version contains the vendor's fix for the vulnerability. Since the attack requires local access with low privileges, enforcing strict access controls and limiting user permissions on systems running Iperius Backup can reduce the attack surface. Employing endpoint protection and monitoring for unusual local activity can help detect potential exploitation attempts. Additionally, organizations should audit and restrict local user accounts to minimize the risk of unauthorized access. Regularly reviewing backup software configurations and applying vendor updates promptly is critical. Network segmentation to isolate backup servers and limiting administrative access further reduce exposure. Finally, educating users about the risks of local privilege misuse and maintaining robust incident response plans will enhance overall resilience.

Description

A flaw has been found in Enter Software Iperius Backup up to 8.7.3. Affected by this vulnerability is an unknown functionality of the component NTLM2 Handler. Executing a manipulation can lead to information disclosure. The attack is restricted to local execution. Attacks of this nature are highly complex. The exploitation appears to be difficult. The exploit has been published and may be used. Upgrading to version 8.7.4 addresses this issue. Upgrading the affected component is advised. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

Impact

The primary impact of CVE-2026-4823 is limited information disclosure, which could potentially expose sensitive data handled by the NTLM2 Handler component within Iperius Backup. Although the vulnerability requires local access and is complex to exploit, an attacker who successfully leverages this flaw could gain insights into system or authentication details that might aid in further attacks or lateral movement within a network. However, the low CVSS score and absence of integrity or availability impacts suggest that the overall risk to organizations is minimal if the vulnerability is promptly addressed. The threat is mainly relevant in environments where attackers have already compromised user-level access, such as insider threats or post-exploitation scenarios. Organizations relying on Iperius Backup for critical backup operations should consider the potential confidentiality risks, especially if backup data or authentication credentials could be exposed.

Summary

CVE-2026-4823 identifies an information disclosure vulnerability in Enter Software's Iperius Backup product, specifically affecting versions 8.7.0 through 8.7.3. The vulnerability resides in an unspecified functionality within the NTLM2 Handler component, which is responsible for handling NTLM authentication processes. An attacker with local access and low privileges can manipulate this component to cause information disclosure. The exact nature of the leaked information is not detailed, but the impact is limited to confidentiality with no reported integrity or availability effects. Exploitation complexity is high, requiring local access and advanced knowledge, and no user interaction is necessary. The vulnerability has a CVSS 4.0 base score of 2.0, reflecting its low severity due to restricted attack vector (local), high attack complexity, and limited impact. The vendor responded promptly and released version 8.7.4 to remediate the flaw. No known active exploits have been reported in the wild, but a proof-of-concept exploit has been published, indicating potential future risk if systems remain unpatched.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Mar 2026, 22:16 UTC

Technical details

References

Community reviews

Related threats