Vendor advisories

Microsoft Security Response Center

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

Current Checked just now 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-2025-2309
MediumCVSS 5.3

HDF5 Type Conversion Logic H5T__bit_copy heap-based overflow

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 hdf5 1.14.4-1 on CBL Mariner 2.0, cbl2 hdf5 1.14.6-1 on CBL Mariner 2.0, azl3 hdf5 1.14.6-2 on Azure Linux 3.0, cbl2 hdf5 1.14.6-2 on CBL Mariner 2.0
Fixed versions1.14.6-6
Vendor guidance

Release Notes

Microsoft Security Response CenterCVE-2025-2308
MediumCVSS 5.3

HDF5 Scale-Offset Filter H5Z__scaleoffset_decompress_one_byte heap-based overflow

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 hdf5 1.14.4.3-1 on Azure Linux 3.0, cbl2 hdf5 1.14.4-1 on CBL Mariner 2.0, cbl2 hdf5 1.14.6-1 on CBL Mariner 2.0, azl3 hdf5 1.14.6-1 on Azure Linux 3.0
Fixed versions1.14.6-6
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