Local null pointer dereference in IOBIt Uninstaller can cause denial of service

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-90485?

CVE-2026-90485 is a vulnerability classified as NULL Pointer Dereference and Improper Resource Shutdown or Release, affecting Uninstaller (affected versions: 15.5.0.11). This vulnerability is rated Medium, with a CVSS score of 6.8. Public exploit code or evidence is available for this vulnerability, but that does not confirm exploitation in the wild.

Overview

Original source data

A flaw has been found in IOBit Uninstaller 15.5.0.11. Affected by this issue is the function sub_11838 of the file IURegistryFilter.sys of the component IOCTL Dispatch Handler. This manipulation causes null pointer dereference. The attack requires local access. The exploit has been published and may be used. Identical IURegistryFilter.sys ships across multiple IObit families. The vendor was contacted early about this disclosure but did not respond in any way.

Affected products and scope

  • IOBIt Uninstaller: version 15.5.0.11 is confirmed affected.
  • IURegistryFilter.sys in other IObit families: identical copies of the file are reported to ship across multiple IObit families. The additional families and affected versions are not named or confirmed.
  • Fixed release: no fixed version is supplied. The status of later or parallel release branches has not been verified.

Technical details

IOBIt Uninstaller contains a flaw in function sub_11838 of the IURegistryFilter.sys driver file, within the IOCTL Dispatch Handler component. Attacker-controlled input is processed in a way that can lead to dereferencing a NULL pointer. The flaw requires local access, and the record describes low privileges and no user interaction. The exact IOCTL, triggering input, and condition that makes the pointer NULL have not been disclosed. Identical IURegistryFilter.sys is reported to ship across multiple IObit families, but the additional product families and their version scope have not been confirmed.

Exploitability

The flaw is locally reachable and is not described as having a remote network attack path. The record describes low privileges, low complexity, and no user interaction. A public exploit or proof of concept has been published, and the advisory describes the exploitation status as proof of concept. This establishes public reproducibility, but the record does not identify a campaign, victim, or specific in-the-wild use.

Technical impact

The documented technical outcome is a null pointer dereference that can cause denial of service and reduce availability of the affected component. The record assigns no confidentiality or integrity impact, does not describe privilege escalation, and does not establish a change in scope to another security authority. Because exploitation requires local access, the practical consequence depends on an attacker already having local execution or interaction capability on the endpoint. The shared driver increases the inventory scope that should be reviewed, but does not by itself confirm that every IObit family is affected.

Business impact

The primary operational risk is loss of availability for the driver or operations that depend on IOBIt Uninstaller. A successful trigger could cause the affected component to fail or stop responding, but impact to the entire host or endpoint is not established. The record does not document data disclosure, data modification, or privilege gain. The issue is most relevant on endpoints where untrusted users or local processes can interact with the product.

Remediation

  1. Identify and address IOBIt Uninstaller installations running version 15.5.0.11, and check other IObit products that install IURegistryFilter.sys.
  2. When the vendor publishes a confirmed fix, upgrade according to the exact branch and release covered by that notice. Do not assume that every later version or parallel branch is safe.
  3. No fixed release or vendor-confirmed technical mitigation is currently supplied. Until guidance is available, consider replacing or removing the affected product where operationally feasible, consistent with the advisory's recommendation to replace the affected object.
  4. Monitor IObit updates and reassess product families that use the same IURegistryFilter.sys before treating them as unaffected.

Detection

  • Inventory IOBIt Uninstaller installations and compare their versions with the affected boundary in affected_summary.
  • Search endpoints for IURegistryFilter.sys and determine which IObit product installed the file.
  • Extend the review to other IObit families if they use the same driver, but do not classify them as affected without confirmed version evidence.
  • Review driver error, crash, or service interruption telemetry involving IURegistryFilter.sys as a precaution. No specific log event, IOC, or signature is confirmed in the record, and the absence of log evidence does not prove safety.
Sources (19)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.