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,536Advisories collected
6,561Published or updated in 30 days
8,317Marked 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,536 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-56847
LowCVSS 3.3

A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects Node.js **22.x**, **24.x**, and **26.x**.

Mariner

Affected productsazl3 nodejs 24.17.0-1 on Azure Linux 3.0
Fixed versions24.18.1-1
Vendor guidance

CBL-Mariner Releases

Microsoft Security Response CenterCVE-2026-56850
MediumCVSS 4.1

A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

Mariner

Affected productsazl3 nodejs 24.17.0-1 on Azure Linux 3.0
Fixed versions24.18.1-1
Vendor guidance

CBL-Mariner Releases

Microsoft Security Response CenterCVE-2025-50076
MediumCVSS 6.5

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). Supported versions that are affected are 8.0.0-8.0.25. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

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 mysql 8.0.42-1, azl3 mysql 8.0.42-1 on Azure Linux 3.0
Microsoft Security Response CenterCVE-2025-7069
LowCVSS 3.3

HDF5 H5FSsection.c H5FS__sect_link_size 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
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
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