Vendor advisories

Microsoft Security Response Center

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

Current Checked 3 hours ago Checked every 6 hours

15,667 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-37236
MediumCVSS 5.3

grpc-gateway v2.28.0 is vulnerable to Incorrect Access Control. The application processes the X-HTTP-Method-Override header in ServeMux.ServeHTTP without restricting allowed methods. When a POST request with Content-Type application/x-www-form-urlencoded includes this header, the request method is rewritten to an arbitrary attacker-supplied value before routing. This allows bypassing method-based access controls enforced by upstream proxies or WAFs.

Mariner

Affected productsazl3 cert-manager 1.12.15-11 on Azure Linux 3.0, azl3 cf-cli 8.7.11-8 on Azure Linux 3.0, azl3 cloud-provider-kubevirt 0.5.1-6 on Azure Linux 3.0, azl3 docker-buildx 0.14.0-16 on Azure Linux 3.0
Fixed versions8.7.11-9, 0.14.0-17, 2.27.0-14, 3.5.35-1
Vendor guidance

Release Notes

Microsoft Security Response CenterCVE-2026-81870
Low

OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs

Mariner

Affected productsazl3 azurelinux-image-tools 1.6.0-2 on Azure Linux 3.0, azl3 cert-manager 1.12.15-12 on Azure Linux 3.0, azl3 containerd2 2.2.4-8 on Azure Linux 3.0, azl3 docker-buildx 0.14.0-16 on Azure Linux 3.0
Fixed versions3.5.35-1, 1.7.0-2, 2.27.0-16, 0.24.2-34
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