Vendor advisories

Microsoft Security Response Center

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

Current Checked 3 hours ago Checked every 6 hours

17,705 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-46598
MediumCVSS 5.3

Invoking pathological inputs can lead to client panic in golang.org/x/crypto/ssh/agent

Mariner

Affected productsazl3 docker-buildx 0.14.0-11 on Azure Linux 3.0, azl3 docker-compose 2.27.0-9 on Azure Linux 3.0, azl3 packer 1.9.5-13 on Azure Linux 3.0, azl3 telegraf 1.31.0-19 on Azure Linux 3.0
Fixed versions1.9.5-14, 2.27.0-13, 1.31.0-23, 0.14.0-15
Vendor guidance

CBL-Mariner Releases

Microsoft Security Response CenterCVE-2026-12448
Severity not listed

Chromium: CVE-2026-12448 Inappropriate implementation in WebView

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 versions149.0.4022.80
Vendor guidance

Release Notes

Microsoft Security Response CenterCVE-2026-12438
Severity not listed

Chromium: CVE-2026-12438 Inappropriate implementation in WebView

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 versions149.0.4022.80
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