Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY19 SECURITY RECORDS

Progress Software

Telerik UI for ASP.NET AJAX

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-19219 2 Sep 2026 2011.2.712 < 2026.3.812 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-18672 2 Sep 2026 2011.2.712 < 2026.3.812 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-14932 22 Jul 2026 2009.1.311 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-14865 22 Jul 2026 2009.1.314 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-13192 22 Jul 2026 2008.3.1314 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-13190 22 Jul 2026 2011.2.712 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-13189 22 Jul 2026 2011.2.712 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13188 22 Jul 2026 2011.2.712 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-13187 22 Jul 2026 2011.2.712 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-13186 22 Jul 2026 2013.1.220 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-13185 22 Jul 2026 2013.1.220 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-13184 22 Jul 2026 2010.1.309 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-13183 22 Jul 2026 2010.1.309 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-13182 22 Jul 2026 2010.1.309 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-13181 22 Jul 2026 2010.1.309 < 2026.2.708 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-6023 22 Apr 2026 2024.4.1114 < 2026.1.421 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-6022 22 Apr 2026 2011.2.712 < 2026.1.421 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-2878 25 Feb 2026 2011.2.712 < 2026.1.225 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2025-3600 14 May 2025 2011.2.712 < 2025.1.416 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.