CVE-2024-43585

Local Code Integrity Guard policy bypass

Published Oct 8, 2024 · Updated Aug 19, 2026

Security feature bypass in Microsoft Windows allows local users to violate Code Integrity Guard policy through an undisclosed mechanism. Microsoft has not published the affected code locus or the operation that mishandles attacker-controlled input. Low-privileged local access is required; successful exploitation changes code-integrity enforcement, with no confidentiality or availability impact reported.

CVSS severity5.5
Medium
EPSS probability0.49%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
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

Security feature bypass in Microsoft Windows allows local users to violate Code Integrity Guard policy through an undisclosed mechanism. Microsoft has not published the affected code locus or the operation that mishandles attacker-controlled input. Low-privileged local access is required; successful exploitation changes code-integrity enforcement, with no confidentiality or availability impact reported.

The record

CVE
CVE-2024-43585
Published
Oct 8, 2024
Updated
Aug 19, 2026
Vendor
Microsoft
Product
Windows Server 2019
Classifications
CWE-693, T1562.001
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 8, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record 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.17763.0 <10.0.17763.6414

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Microsoft · Windows Server 2019version=10.0.17763.0 <10.0.17763.6414
Microsoft · Windows 11, version 24H2version=10.0.26100.0 <10.0.26100.2033
Microsoft · Windows 11 version 21H2version=10.0.22000.0 <10.0.22000.3260
Microsoft · Windows 10 Version 21H2version=10.0.19043.0 <10.0.19044.5011
Microsoft · Windows Server 2022, 23H2 Edition (Server Core installation)version=10.0.25398.0 <10.0.25398.1189
Microsoft · Windows 11 Version 22H3version=10.0.22631.0 <10.0.22631.4317
Microsoft · Windows 10 Version 22H2version=10.0.19045.0 <10.0.19045.5011
Microsoft · Windows Server 2019 (Server Core installation)version=10.0.17763.0 <10.0.17763.6414
Microsoft · Windows 11 Version 23H2version=10.0.22631.0 <10.0.22631.4317
Microsoft · Windows 11, version 22H2version=10.0.22621.0 <10.0.22621.4317
Microsoft · Windows Server 2022version=10.0.20348.0 <10.0.20348.2762
Microsoft · Windows 10 Version 1809version=10.0.17763.0 <10.0.17763.6414

Published CVSS scores

5.5MicrosoftCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-693Protection Mechanism Failure
T1562.001Impair Defenses: Disable or Modify Tools

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.

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