Vendor advisories

Microsoft Security Response Center

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

Current Checked 3 minutes 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-40361
CriticalCVSS 8.4

Microsoft Outlook and Word Remote Code Execution Vulnerability

Use after free in Microsoft Office allows an unauthorized attacker to execute code locally.

Affected productsMicrosoft Office 2019 for 32-bit editions, Microsoft Office 2019 for 64-bit editions, Microsoft 365 Apps for Enterprise for 32-bit Systems, Microsoft 365 Apps for Enterprise for 64-bit Systems
Fixed versionshttps://aka.ms/OfficeSecurityReleases, 16.109.26051019, 16.0.5552.1000
Vendor guidance

Click to Run Release Notes Install KB5002858.

Microsoft Security Response CenterCVE-2026-21711
MediumCVSS 5.3

A flaw in Node.js Permission Model network enforcement leaves Unix Domain Socket (UDS) server operations without the required permission checks, while all comparable network paths correctly enforce them. As a result, code running under `--permission` without `--allow-net` can create and expose local IPC endpoints, allowing communication with other processes on the same host outside of the intended network restriction boundary. This vulnerability affects Node.js **25.x** processes using the Permission Model where `--allow-net` is intentionally omitted to restrict network access. Note that `--allow-net` is currently an experimental feature.

Mariner

Affected productsazl3 nodejs24 24.14.1-2 on Azure Linux 3.0, azl3 nodejs24 24.13.0-3 on Azure Linux 3.0, azl3 nodejs24 24.14.1-1 on Azure Linux 3.0
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