Missing Microsoft Windows Security Updates
Windows hosts are missing security updates that Microsoft has released, leaving known and often actively exploited operating system vulnerabilities unfixed.
| Severity | High |
| CVSS 3.1 | 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator |
| CVSS 4.0 | 9.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1210 Exploitation of Remote Services, T1068 Exploitation for Privilege Escalation, T1203 Exploitation for Client Execution |
| Category | Outdated Components |
Description
One or more Windows hosts have not installed security updates that Microsoft has already released. Microsoft publishes Windows security fixes on the second Tuesday of each month, and for current Windows releases each monthly update is cumulative, so a host that has missed one update usually lacks every fix released since it was last updated. Hosts usually fall behind because they are outside the scope of the update management tool, their Windows Update agent is failing, or a deferral or exclusion was never removed.
The fixes typically address remote code execution in network-facing components, elevation of privilege flaws that let a standard user or service account gain SYSTEM rights, and weaknesses in authentication and cryptographic components. An attacker who can reach a host with missing updates can use published exploits for the unfixed vulnerabilities: depending on which updates are missing, they may run code on the host remotely without credentials, or a standard user, or malware running as one, may gain full administrative control of the host and harvest the credentials stored on it for lateral movement. Windows vulnerabilities are among the most numerous in CISA's Known Exploited Vulnerabilities (KEV) catalogue, and exploits for many of them are built into commodity attack tools and ransomware. The risk is greatest for domain controllers, internet-facing servers and hosts used by many people, and grows the longer updates are outstanding; network restrictions and endpoint protection may block particular exploits but do not remove the vulnerabilities.
The condition is usually identified by an authenticated vulnerability scan, which reads the installed updates and file versions on each host and reports one result for each missing update or advisory, so a single host several months behind can produce dozens of results with one cause. Unauthenticated scans infer missing updates from the behaviour of exposed services and are less reliable. Results can be confirmed from the host's update history or with Get-HotFix. Some fixes are shipped disabled and take effect only once a registry value is set, as with the signature padding check for CVE-2013-3900 (EnableCertPaddingCheck); scanners report these as missing even on fully updated hosts until the setting is applied.
Remediation
Bring every host up to date and keep it there:
- Install the latest cumulative security update on each affected host, with any servicing stack update Microsoft lists as a prerequisite, and restart the host so that the update takes effect. Microsoft's Security Update Guide lists each update and the CVEs it fixes.
- Find out why each host fell behind, for example a failing Windows Update agent, a host missing from the scope of WSUS, Configuration Manager, Intune or Windows Update for Business, or a pause or deferral that was never lifted, and correct the cause rather than updating the host once by hand.
- Apply any registry or configuration change that an advisory requires before its fix is active, and add it to the build standard so that new hosts receive it.
- Run a patch management process with defined timescales, for example installing high and critical updates within 14 days of release as Cyber Essentials requires, sooner for vulnerabilities that are being exploited or are listed in the KEV catalogue, and report on hosts that are not current.
Where a host cannot be updated promptly, restrict its network exposure to the systems that need it, disable services and features it does not use, and monitor it closely until the update is installed. Confirm the fix by repeating the authenticated scan and checking that each host reports the current cumulative update.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.