Vendor advisories

Microsoft Security Response Center

Browse 15,667 advisories from this official source. Search by product, CVE, severity, or advisory ID.

Current Checked 49 minutes ago Checked every 6 hours

15,667 advisories

Each date says whether the vendor published or updated the bulletin. A vendor bulletin describes products that may be affected. It does not prove that the vulnerable product or version is installed in your environment.

RSS for these results
Microsoft Security Response CenterCVE-2026-83862
HighCVSS 8.8

Windows Network Load Balancing Remote Code Execution Vulnerability

Use after free in Windows Network Load Balancing allows an unauthorized attacker to execute code over an adjacent network.

Affected productsWindows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows Server 2019, Windows Server 2019 (Server Core installation)
Fixed versions10.0.17763.9376, 10.0.20348.5761, 10.0.26100.33650, 10.0.14393.9612
Vendor guidance

Install KB5126651. Install KB5126655. Install KB5126646. Install KB5126868. Install KB5126835. Install KB5126836.

Microsoft Security Response CenterCVE-2026-102208
HighCVSS 7.0

Windows Win32 Kernel Subsystem Elevation of Privilege Vulnerability

Use after free in Windows Win32 Kernel Subsystem allows an authorized attacker to elevate privileges locally.

Affected productsWindows Server 2012, Windows Server 2012 (Server Core installation), Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation)
Fixed versions6.2.9200.26434, 6.3.9600.23470, 10.0.14393.9612, 10.0.17763.9376
Vendor guidance

Install KB5126835. Install KB5126836. Install KB5126868. Install KB5126651. Install KB5126657. Install KB5126655. Install KB5126653.

Before you act

Start with the vendor's bulletin.

We normalize the fields that vendors publish so you can search and compare advisories in one place. We do not replace the original bulletin or turn a product-name match into proof that a system is vulnerable.

Confirm the installed product and version, read the linked vendor guidance, and test the recommended update or mitigation through your normal change process.

How we check our sources