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
18,986Advisories collected
6,818Published or updated in 30 days
8,727Marked 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.

18,986 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-6965
HighCVSS 9.8

Integer Truncation on SQLite

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 sqlite 3.39.2-4 on CBL Mariner 2.0, Microsoft Visual Studio 2026 version 18.5, azl3 sqlite 3.44.0-2 on Azure Linux 3.0, cbl2 sqlite 3.39.2-3 on CBL Mariner 2.0
Fixed versions3.39.2-4, 18.5.3, 3.44.0-2, 10.0.17763.8276
Vendor guidance

CBL-Mariner Releases Release Notes Install KB5073723. Install KB5073457. Install KB5073724. Install KB5073379. Install KB5074109. Install KB5073455. Install KB5073450. Install KB5073722.

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