Vendor advisories

Microsoft Security Response Center

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

Current Checked 5 hours ago Checked every 6 hours

17,776 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-9880
Severity not listed

Chromium: CVE-2026-9880 Insufficient validation of untrusted input in WebGL

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 versions148.0.3967.97
Vendor guidance

Release Notes

Microsoft Security Response CenterCVE-2026-9977
Severity not listed

Chromium: CVE-2026-9977 Insufficient validation of untrusted input in WebShare

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 versions148.0.3967.97
Vendor guidance

Release Notes

Microsoft Security Response CenterCVE-2026-9969
Severity not listed

Chromium: CVE-2026-9969 Insufficient validation of untrusted input in ANGLE

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 versions148.0.3967.97
Vendor guidance

Release Notes

Microsoft Security Response CenterCVE-2025-13227
HighCVSS 8.6

Type Confusion in V8 in Google Chrome prior to 142.0.7444.59 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Mariner

Affected productsazl3 nodejs 20.14.0-9 on Azure Linux 3.0, azl3 nodejs 20.14.0-10 on Azure Linux 3.0, azl3 nodejs 20.14.0-14 on Azure Linux 3.0, azl3 nodejs 20.14.0-13 on Azure Linux 3.0
Fixed versions24.14.1-3
Vendor guidance

CBL-Mariner Releases

Microsoft Security Response CenterCVE-2024-22018
MediumCVSS 2.9

A vulnerability has been identified in Node.js, affecting users of the experimental permission model when the --allow-fs-read flag is used. This flaw arises from an inadequate permission model that fails to restrict file stats through the fs.lstat API. As a result, malicious actors can retrieve stats from files that they do not have explicit read access to. This vulnerability affects all users using the experimental permission model in Node.js 20 and Node.js 21. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability? One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the mos...

Affected productsazl3 nodejs 20.14.0-15 on Azure Linux 3.0
Fixed versions24.14.1-3
Vendor guidance

CBL-Mariner Releases

Microsoft Security Response CenterCVE-2026-10021
Severity not listed

Chromium: CVE-2026-10021 Insufficient validation of untrusted input in USB

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 versions148.0.3967.96
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