CVE-2026-50302 | Windows Cryptographic Services Security Feature Bypass Vulnerability

Improper certificate validation in Windows Cryptographic Services allows an unauthorized attacker to bypass a security feature over a network.

Published: 2026-07-14 Last update: 2026-07-22 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-50302 is rated Low Risk (22.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.24%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-50302

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-07-15 — 0.24% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-50302

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.2 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.6 2.5 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 2.5 [email protected]

Weakness enumeration for CVE-2026-50302

GitHub Security Advisory for CVE-2026-50302

GHSA-h8h9-72c6-9q22 · Severity: medium — Improper certificate validation in Windows Cryptographic Services allows an unauthorized attacker...

Affected software / configurations for CVE-2026-50302

Vendor Product Version Raw CPE
microsoft windows_10_21h2 < 10.0.19044.7548 cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:arm64:*
microsoft windows_10_21h2 < 10.0.19044.7548 cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:x64:*
microsoft windows_10_21h2 < 10.0.19044.7548 cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:x86:*
microsoft windows_10_22h2 < 10.0.19045.7548 cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:arm64:*
microsoft windows_10_22h2 < 10.0.19045.7548 cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:x64:*
microsoft windows_10_22h2 < 10.0.19045.7548 cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:x86:*
microsoft windows_11_24h2 < 10.0.26100.8875 cpe:2.3:o:microsoft:windows_11_24h2:*:*:*:*:*:*:arm64:*
microsoft windows_11_24h2 < 10.0.26100.8875 cpe:2.3:o:microsoft:windows_11_24h2:*:*:*:*:*:*:x64:*
microsoft windows_11_25h2 < 10.0.26200.8875 cpe:2.3:o:microsoft:windows_11_25h2:*:*:*:*:*:*:arm64:*
microsoft windows_11_25h2 < 10.0.26200.8875 cpe:2.3:o:microsoft:windows_11_25h2:*:*:*:*:*:*:x64:*
microsoft windows_11_26h1 < 10.0.28000.2269 cpe:2.3:o:microsoft:windows_11_26h1:*:*:*:*:*:*:x64:*
microsoft windows_11_26h1 < 10.0.28000.2525 cpe:2.3:o:microsoft:windows_11_26h1:*:*:*:*:*:*:arm64:*
microsoft windows_server_2022 < 10.0.20348.5386 cpe:2.3:o:microsoft:windows_server_2022:*:*:*:*:*:*:*:*
microsoft windows_server_2025 < 10.0.26100.33158 cpe:2.3:o:microsoft:windows_server_2025:*:*:*:*:*:*:*:*

References for CVE-2026-50302

cvelogic Threat Intelligence