Vendor advisories

Microsoft Security Response Center

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

Current Checked 4 hours ago Checked every 6 hours

15,888 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-100212
HighCVSS 8.8

Microsoft Office Excel Remote Code Execution Vulnerability

Use after free in Microsoft Office Excel allows an unauthorized attacker to execute code over a network.

Affected productsMicrosoft Office LTSC 2021 for 64-bit editions, Microsoft Office LTSC 2021 for 32-bit editions, Microsoft Office LTSC 2024 for 64-bit editions, Microsoft Office LTSC 2024 for 32-bit editions
Fixed versions16.0.14334.20974, 16.0.17932.21056, https://aka.ms/OfficeSecurityReleases, 16.114.26101123
Vendor guidance

Release Notes Install KB5002928.

Microsoft Security Response CenterCVE-2026-92707
MediumCVSS 5.3

MessagePack-CSharp Denial of Service Vulnerability

Improperly controlled sequential memory allocation in .NET allows an unauthorized attacker to deny service over a network.

Affected productsMicrosoft.AspNetCore.SignalR.Protocols.MessagePack on .NET 10.0 runtime installed on Windows, Microsoft.AspNetCore.SignalR.Protocols.MessagePack on .NET 10.0 runtime installed on Linux, Microsoft.AspNetCore.SignalR.Protocols.MessagePack on .NET 10.0 runtime installed on Mac OS, Microsoft.AspNetCore.SignalR.Protocols.MessagePack on .NET 11.0 runtime installed on Windows
Fixed versions10.0.13, 11.0.0-rc.2, 8.0.32, 9.0.21
Vendor guidance

Release Notes

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