Vendor advisories

Microsoft Security Response Center

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

Current Checked 5 hours ago Checked every 6 hours

17,903 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-6312
Severity not listed

Chromium: CVE-2026-6312 Insufficient policy enforcement in Passwords

This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.

Affected productsMicrosoft Edge (Chromium-based)
Fixed versions147.0.3912.72
Vendor guidance

Release Notes

Microsoft Security Response CenterCVE-2026-23666
CriticalCVSS 7.5

.NET Framework Denial of Service Vulnerability

Improper input validation in .NET Framework allows an unauthorized attacker to deny service over a network.

Affected productsMicrosoft .NET Framework 4.8 on Windows 10 Version 1607 for 32-bit Systems, Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for x64-based Systems, Microsoft .NET Framework 4.8 on Windows Server 2012, Microsoft .NET Framework 4.8 on Windows Server 2012 (Server Core installation)
Fixed versions4.8.4801.0, 2.0.50727.9068 & 3.0.30729.9065 & 4.8.4801.0, 2.0.50727.9181 & 3.0.30729.9165 & 4.8.4801.0, 2.0.50727.9068 & 3.0.30729.9065 & 4.7.4141.0
Vendor guidance

Install KB5082411. Install KB5082403. Install KB5082404. Install KB5082414. Install KB5082427. Install KB5082426. Install KB5082413. Install KB5082400. Install KB5082402. Install KB5082425. Install KB5082419. Install ...

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