Vendor advisories

Security advisories from the vendors you use.

Search new and updated bulletins from Microsoft, Citrix, Cisco, Palo Alto Networks, Fortinet, Ivanti, Delinea, Ubuntu, and AWS. We keep each vendor's advisory ID, affected products, CVEs, severity, dates, and available fix guidance together.

11Vendor sources
16,745Advisories collected
6,299Published or updated in 30 days
6,969Marked critical or high
Coverage

Connected directly to official vendor sources

The original vendor bulletin remains the authority. SecurityAlert gives you one place to find it and compare the details vendors publish in different formats.

16,745 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-35189
MediumCVSS 5.3

Excessive Memory Allocation in Relative CRLDP Processing

Mariner

Affected productsazl3 edk2 20240524git3e722403cd16-20 on Azure Linux 3.0, azl3 openssl 3.3.7-6 on Azure Linux 3.0, azl3 shim-unsigned-aarch64 16.1-2 on Azure Linux 3.0, azl3 shim-unsigned-x64 16.1-2 on Azure Linux 3.0
Fixed versions20240524git3e722403cd16-21, 3.3.7-7
Vendor guidance

Release Notes

Microsoft Security Response CenterCVE-2026-28390
MediumCVSS 7.5

Possible NULL Dereference When Processing CMS KeyTransportRecipientInfo

Mariner

Affected productsazl3 edk2 20240524git3e722403cd16-16 on Azure Linux 3.0, azl3 openssl 3.3.5-4 on Azure Linux 3.0, azl3 edk2 20240524git3e722403cd16-15 on Azure Linux 3.0, azl3 nodejs24 24.13.0-3 on Azure Linux 3.0
Fixed versions20240524git3e722403cd16-16, 3.3.5-5, 1.1.1k-40
Vendor guidance

CBL-Mariner Releases 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