Vendor advisories

Microsoft Security Response Center

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

Current Checked 29 minutes ago Checked every 6 hours

15,711 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-56862
MediumCVSS 7.5

Limit handshake messages we are willing to accept post-handshake in crypto/tls

Mariner

Affected productsazl3 python-tensorboard 2.16.2-6 on Azure Linux 3.0, azl3 tensorflow 2.16.1-11 on Azure Linux 3.0, azl3 gcc 13.2.0-7 on Azure Linux 3.0, azl3 golang 1.25.12-1 on Azure Linux 3.0
Vendor guidance

See the Microsoft Security Update Guide for the update that applies to your product.

Microsoft Security Response CenterCVE-2026-56859
MediumCVSS 7.5

Add recursion depth guard during decode in encoding/xml

Mariner

Affected productsazl3 gcc 13.2.0-7 on Azure Linux 3.0, azl3 golang 1.25.12-1 on Azure Linux 3.0, azl3 golang 1.26.5-2 on Azure Linux 3.0, azl3 python-tensorboard 2.16.2-6 on Azure Linux 3.0
Vendor guidance

See the Microsoft Security Update Guide for the update that applies to your product.

Microsoft Security Response CenterCVE-2026-56855
MediumCVSS 7.5

Prevent DoS on deadlocked established channel in golang.org/x/crypto/ssh

Mariner

Affected productsazl3 kubevirt 1.7.1-8 on Azure Linux 3.0, azl3 packer 1.9.5-18 on Azure Linux 3.0, azl3 cf-cli 8.7.11-9 on Azure Linux 3.0, azl3 docker-buildx 0.14.0-17 on Azure Linux 3.0
Fixed versions8.7.11-9, 0.14.0-17, 2.27.0-14, 1.30.10-30
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