Skip to main content
CVE-2024-43550VulnerabilityPublished Updated

CVE-2024-43550: Microsoft Windows 10 Version 1507 · Improper Certificate Validation

Affects Microsoft Windows 10 Version 1507Source GCVE Database

0

Not known to be exploited · CVSS 7.4 High · patch available : patch Microsoft Windows 10 Version 1507 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Microsoft Windows 10 Version 1507Affected
  • =10.0.10240.0
Fixed in–

AI-suggested

An official fix is available from Microsoft for Windows 10 Version 1507 (build 10.0.10240.0). Users and administrators should apply the security update provided by Microsoft to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2024-43550 is a high severity vulnerability in Microsoft Windows 10 Version 1507 involving improper certificate validation in the Windows Secure Channel component. This flaw can allow an attacker to spoof secure channel communications, potentially leading to unauthorized access or data compromise. An official fix is available from Microsoft to address this issue.

References

Community reviews

Loading reviews…