/

CVE-2026-90493

Severity:

HIGH RISK

(8.8)

Improper Access Control (CWE-284) in IDM Kernel Driver

CVE-2026-90493

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-266, CWE-284

Impact:

Local Privilege Escalation and Unauthorized Registry Modification

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Internet Download Manager for Windows exposes a kernel-driver interface that grants authenticated local users broad access to registry operations without adequately enforcing registry permissions. A low-privileged local user may use this interface to modify protected system configuration, potentially enabling privilege escalation, persistence, or broader compromise.

Affected context

The vulnerability occurs in the idmwfp.sys kernel driver installed by affected Internet Download Manager deployments on Windows. Risk is present where the driver device interface is accessible to authenticated local users and its registry-operation handlers accept caller-controlled paths or values without limiting access to IDM-owned namespaces or rechecking the caller's Windows registry permissions.

Exploit preconditions

  • Attack surface: The locally accessible \\.\IDMWFP device interface exposed by the Windows kernel driver
  • Required access: A low-privileged authenticated local Windows account
  • Trigger point: Registry-operation requests processed by the driver's relevant IOCTL handler
  • Why exploitation is possible: The driver grants broad device access and performs registry operations without adequately authenticating the caller, enforcing registry ACLs, or restricting access to approved registry namespaces

Why this happens

The underlying bug is an authorization failure in a privileged kernel component. The driver exposes sensitive registry functionality to authenticated users and treats caller-supplied registry targets as authorized without applying an independent security boundary. This behavior maps primarily to CWE-284: Improper Access Control and is also related to CWE-266: Incorrect Privilege Assignment, because a privileged driver performs operations beyond the caller's intended authority.

Potential impact

  • A local attacker may modify registry values consumed by privileged services or drivers
  • The vulnerability could enable local privilege escalation
  • An attacker may establish high-privilege persistence
  • Sensitive system or user configuration may be disclosed
  • System integrity, confidentiality, or availability may be compromised
  • Registry tampering could disrupt applications or security controls

General mitigation guidance

Mitigation generally focuses on reducing the authority exposed through kernel-driver interfaces and enforcing authorization at every privileged operation.

Common defensive patterns include:

  • Restricting device-object access to only the identities and operations that require it
  • Applying explicit authorization checks before every registry action
  • Limiting registry access to narrowly defined, product-owned namespaces
  • Validating and canonicalizing registry paths before use
  • Avoiding privileged driver functionality when a user-mode, least-privilege alternative is suitable
  • Running related services and components with the minimum required privileges
  • Preventing untrusted users from loading, invoking, or reconfiguring privileged components
  • Monitoring and protecting registry locations used by privileged services

How teams detect issues like this

Detection approaches can include:

  • Static analysis for kernel IOCTL handlers that perform registry operations without caller authorization checks
  • Code review of device-object security descriptors and access-control initialization
  • Searches for registry APIs reached from user-controlled IOCTL input
  • Review signals such as unrestricted registry paths, missing namespace validation, or reliance solely on device-level access checks
  • Runtime monitoring for unusual registry changes originating from the driver device interface
  • Policy enforcement that restricts privileged driver interfaces to approved identities and operations
  • Automated security review tools that flag privilege-boundary crossings and missing authorization checks

Sources

SourceLink
github.comgithub.com/KnCRJVirX/IDM_LPE_PoC/blob/main/report_en.md
github.comgithub.com/KnCRJVirX/IDM_LPE_PoC/tree/main/poc
vuldb.comvuldb.com/cve/CVE-2026-90493
vuldb.comvuldb.com/submit/891910
vuldb.comvuldb.com/vuln/403081
vuldb.comvuldb.com/vuln/403081/cti

Frequently asked

questions

Exploitation is primarily local because the attacker must access the driver's device interface from the affected Windows system. Remote impact could occur indirectly if an attacker first obtains local access through another vulnerability or compromised account.

A low-privileged authenticated local Windows account is generally sufficient when the driver interface grants access to authenticated users.

The safest pattern is to enforce authorization inside the driver for every registry operation, restrict access to approved namespaces, and expose only the minimum functionality required by the product.

Treat kernel-driver IOCTLs as privileged APIs, review device-object security descriptors, validate all caller-controlled paths, apply least privilege, and test authorization boundaries during code review and security assessment.

Find out what's already
exploitable in your codebase.