A security feature bypass vulnerability exists in Windows 10 when third party filters are called during a password update, aka 'Windows Sec…

published 2020-01-14 6y ago modified 2026-06-17 4mo ago also EUVD-2020-2115

cvss: 4.4; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits: 0; none known

A security feature bypass vulnerability exists in Windows 10 when third party filters are called during a password update, aka 'Windows Security Feature Bypass Vulnerability'.

Patch / fix

links 1

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0621 advisory

Is CVE-2020-0621 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	4.4	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:N/I:P/A:N

Affected products

Microsoft Windows
Microsoft Windows Server

Classification

Weakness

CWE-613 DEPRECATED: Insufficient Session Expiration

References

portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2020-0621
patch, vendor-advisory

Sources

CVE List CVE-2020-0621
NVD CVE-2020-0621

Fencer Intel 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.