Search threats, CVEs… ⌘K
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.

Set up product alerts Follow the RSS feed
11Vendor sources
16,884Advisories collected
6,318Published or updated in 30 days
6,999Marked 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,884 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-41254
MediumCVSS 4.0

Little CMS (lcms2) through 2.18 has an integer overflow in CubeSize in cmslut.c because the overflow check is performed after the multiplication.

Mariner

Affected productsazl3 lcms2 2.15-2 on Azure Linux 3.0, cbl2 lcms2 2.13.1-2 on CBL Mariner 2.0, azl3 lcms2 2.15-1 on Azure Linux 3.0, cbl2 lcms2 2.13.1-2 on CBL-Mariner 2.0
Fixed versions2.15-2
Vendor guidance

CBL-Mariner Releases Release Notes

CVE-2026-41254
Read the vendor advisory Watch this product
Microsoft Security Response CenterCVE-2026-5160
MediumCVSS 6.1

Versions of the package github.com/yuin/goldmark/renderer/html before 1.7.17 are vulnerable to Cross-site Scripting (XSS) due to improper ordering of URL validation and normalization. The renderer validates link destinations using a prefix-based check (IsDangerousURL) before resolving HTML entities. This allows an attacker to bypass protocol filtering by encoding dangerous schemes using HTML5 named character references. For example, a payload such as javascript:alert(1) is not recognized as dangerous during validation, leading to arbitrary script execution in the context of applications that render the URL.

Mariner

Affected productscbl2 gh 2.13.0-26 on CBL Mariner 2.0, azl3 telegraf 1.31.0-17 on Azure Linux 3.0, azl3 gh 2.62.0-15 on Azure Linux 3.0, azl3 telegraf 1.31.0-19 on Azure Linux 3.0
Fixed versions1.31.0-19, 2.62.0-15
Vendor guidance

CBL-Mariner Releases Release Notes

CVE-2026-5160
Read the vendor advisory Watch this product
Microsoft Security Response CenterCVE-2026-2739
Medium

This affects versions of the package bn.js before 5.2.3. Calling maskn(0) on any BN instance corrupts the internal state, causing toString(), divmod(), and other methods to enter an infinite loop, hanging the process indefinitely.

Mariner

Affected productscbl2 reaper 3.1.1-22 on CBL Mariner 2.0, cbl2 reaper 3.1.1-22 on CBL-Mariner 2.0
Fixed versions3.1.1-23
Vendor guidance

CBL-Mariner Releases Release Notes

CVE-2026-2739
Read the vendor advisory Watch this product
Microsoft Security Response CenterCVE-2025-38728
HighCVSS 7.1

smb3: fix for slab out of bounds on mount to ksmbd

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 kernel 6.6.96.2-1 on Azure Linux 3.0, azl3 kernel 6.6.96.2-2 on Azure Linux 3.0, cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0, cbl2 kernel 5.15.202.1-1
Fixed versions6.6.104.2-1
Vendor guidance

CBL-Mariner Releases Release Notes

CVE-2025-38728
Read the vendor advisory Watch this product
Microsoft Security Response CenterCVE-2026-41035
HighCVSS 7.4

In rsync 3.0.1 through 3.4.1, receive_xattr relies on an untrusted length value during a qsort call, leading to a receiver use-after-free. The victim must run rsync with -X (aka --xattrs). On Linux, many (but not all) common configurations are vulnerable. Non-Linux platforms are more widely vulnerable.

Mariner

Affected productsazl3 rsync 3.4.1-2 on Azure Linux 3.0, cbl2 rsync 3.4.1-2 on CBL Mariner 2.0, cbl2 rsync 3.4.1-2 on CBL-Mariner 2.0
Fixed versions3.4.3-1
Vendor guidance

CBL-Mariner Releases Release Notes

CVE-2026-41035
Read the vendor advisory Watch this product
Microsoft Security Response CenterCVE-2025-38679
HighCVSS 7.1

media: venus: Fix OOB read due to missing payload bound check

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 kernel 6.6.96.2-2 on Azure Linux 3.0, cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0, cbl2 kernel 5.15.200.1-1 on CBL Mariner 2.0, cbl2 kernel 5.15.202.1-1 on CBL Mariner 2.0
Fixed versions6.6.104.2-1
Vendor guidance

CBL-Mariner Releases Release Notes

CVE-2025-38679
Read the vendor advisory Watch this product
Microsoft Security Response CenterCVE-2025-38422
HighCVSS 7.8

net: lan743x: Modify the EEPROM and OTP size for PCI1xxxx devices

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 kernel 6.6.96.1-1 on Azure Linux 3.0, cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0, cbl2 kernel 5.15.202.1-1 on CBL Mariner 2.0, azl3 kernel 6.6.92.2-2 on Azure Linux 3.0
Fixed versions6.6.96.1-1
Vendor guidance

CBL-Mariner Releases Release Notes

CVE-2025-38422
Read the vendor advisory Watch this product
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