CVE-2024-26234Known exploitation

Malicious-code trust via valid driver signature

Published Apr 9, 2024 · Updated May 3, 2025

Spoofing in Microsoft Windows Proxy Driver allows local users with high privileges to run malicious code trusted by Windows. A malicious executable obtained a valid Windows Hardware Compatibility Publisher signature, so Windows accepted it as signed code until the associated files were revoked. Administrator-level execution is required to install and start the CatalogWatcher service; its backdoor embeds 3proxy to monitor or intercept network traffic.

CVSS severity6.7
Medium
EPSS probability4.85%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Spoofing in Microsoft Windows Proxy Driver allows local users with high privileges to run malicious code trusted by Windows. A malicious executable obtained a valid Windows Hardware Compatibility Publisher signature, so Windows accepted it as signed code until the associated files were revoked. Administrator-level execution is required to install and start the CatalogWatcher service; its backdoor embeds 3proxy to monitor or intercept network traffic.

The record

CVE
CVE-2024-26234
Published
Apr 9, 2024
Updated
May 3, 2025
Vendor
Microsoft
Product
Windows 10 Version 1507
Classifications
CWE-284, T1553.002
Attack vector
local
Privileges
admin

Timeline

How it unfolded

  1. Dec 1, 2023Exploitation reportedMalicious WHCP-signed CatalogWatcher backdoor observed
  2. Apr 9, 2024CVE publishedPublication date reported by the CVE source.
  3. May 3, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=10.0.10240.0 <10.0.10240.20596

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

Microsoft · Windows 10 Version 1507version=10.0.10240.0 <10.0.10240.20596
Microsoft · Windows Server 2019version=10.0.17763.0 <10.0.17763.5696
Microsoft · Windows Server 2016 (Server Core installation)version=10.0.14393.0 <10.0.14393.6897
Microsoft · Windows 11 version 21H2version=10.0.0 <10.0.22000.2899
Microsoft · Windows Server 2012 (Server Core installation)version=6.2.9200.0 <6.2.9200.24821
Microsoft · Windows Server 2012version=6.2.9200.0 <6.2.9200.24821
Microsoft · Windows 10 Version 21H2version=10.0.19043.0 <10.0.19044.4291
Microsoft · Windows Server 2022, 23H2 Edition (Server Core installation)version=10.0.25398.0 <10.0.25398.830
Microsoft · Windows Server 2016version=10.0.14393.0 <10.0.14393.6897
Microsoft · Windows 11 Version 22H3version=10.0.22631.0 <10.0.22631.3447
Microsoft · Windows Server 2008 R2 Service Pack 1version=6.1.7601.0 <6.1.7601.27067
Microsoft · Windows Server 2008 R2 Service Pack 1 (Server Core installation)version=6.1.7601.0 <6.1.7601.27067
Microsoft · Windows 10 Version 22H2version=10.0.19045.0 <10.0.19045.4291
Microsoft · Windows Server 2012 R2 (Server Core installation)version=6.3.9600.0 <6.3.9600.21924
Microsoft · Windows Server 2019 (Server Core installation)version=10.0.17763.0 <10.0.17763.5696
Microsoft · Windows 11 Version 23H2version=10.0.22631.0 <10.0.22631.3447
Microsoft · Windows 11, version 22H2version=10.0.22621.0 <10.0.22621.3447
Microsoft · Windows 10 Version 1607version=10.0.14393.0 <10.0.14393.6897
Microsoft · Windows Server 2008 Service Pack 2version=6.0.6003.0 <6.0.6003.22618
Microsoft · Windows Server 2022version=10.0.20348.0 <10.0.20348.2402
Microsoft · Windows 10 Version 1809version=10.0.0 <10.0.17763.5696; version=10.0.17763.0 <10.0.17763.5696
Microsoft · Windows Server 2012 R2version=6.3.9600.0 <6.3.9600.21924
Microsoft · Windows Server 2008 Service Pack 2 (Server Core installation)version=6.0.6003.0 <6.0.6003.22618

Published CVSS scores

6.7Microsoft CorporationCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesadmin
Known exploitationReported
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-284Improper Access Control
T1553.002Subvert Trust Controls: Code Signing

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Reported exploitation

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo