CVE-2026-50302 json
Windows Cryptographic Services Security Feature Bypass Vulnerability
published 2026-07-14 3 mo ago modified 2026-11-01 7 d ago also EUVD-2026-43848
- cvss
- 4.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
Improper certificate validation in Windows Cryptographic Services allows an unauthorized attacker to bypass a security feature over a network.
Patch / fix
- Microsoft Windows 10 Version 21H2 10.0.19044.7548
- Microsoft Windows 10 Version 22H2 10.0.19045.7548
- Microsoft Windows 11 Version 24H2 10.0.26100.8875
- Microsoft Windows 11 Version 25H2 10.0.26200.8875
- Microsoft Windows 11 version 26H1 10.0.28000.2525
- Microsoft Windows Server 2022 10.0.20348.5386
- Microsoft Windows Server 2025 10.0.26100.33158
- Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.33158
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N/E:U/RL:O/RC:C |
| CNA | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected products
- Microsoft Windows 10 Version 21H2
- Microsoft Windows 10 Version 22H2
- Microsoft Windows 11 Version 24H2
- Microsoft Windows 11 Version 25H2
- Microsoft Windows 11 version 26H1
- Microsoft Windows Server 2022
- Microsoft Windows Server 2025
- Microsoft Windows Server 2025 (Server Core installation)
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-50302
vendor-advisory, patch
Sources
- CVE List CVE-2026-50302
- NVD CVE-2026-50302
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.