Vendor advisories

Microsoft Security Response Center

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

Current Checked 5 hours ago Checked every 6 hours

17,461 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-2025-11840
LowCVSS 3.3

GNU Binutils ldmisc.c vfinfo out-of-bounds

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 productscbl2 binutils 2.37-17 on CBL Mariner 2.0, cbl2 binutils 2.37-19 on CBL Mariner 2.0
Microsoft Security Response CenterCVE-2024-31745
Severity not listed

CVE-2024-31745

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 productscbl2 libdwarf 0.9.0-3, azl3 libdwarf 0.9.0-1 on Azure Linux 3.0
Microsoft Security Response CenterCVE-2019-11939
HighCVSS 7.5

Golang Facebook Thrift servers would not error upon receiving messages declaring containers of sizes larger than the payload. As a result, malicious clients could send short messages which would result in a large memory allocation, potentially leading to denial of service. This issue affects Facebook Thrift prior to v2020.03.16.00.

Mariner

Affected productsazl3 thrift 0.15.0-5 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