CVE-2026-13187
CVE-2026-13187 is a high-severity vulnerability in Progress Telerik Ui For Asp.net Ajax with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-470.
Key facts
- Severity: High (CVSS 3.x base score 8.1)
- EPSS exploit prediction: 0% (27th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-470
- Affected product: Progress Telerik Ui For Asp.net Ajax
- Published:
- Last modified:
Description
In Progress® Telerik® UI for AJAX prior to v2026.2.708, DialogHandler provider type input may be tampered with, potentially altering dialog processing and enabling chained exploitation.
Frequently asked questions
- What is CVE-2026-13187?
- In Progress® Telerik® UI for AJAX prior to v2026.2.708, DialogHandler provider type input may be tampered with, potentially altering dialog processing and enabling chained exploitation.
- How severe is CVE-2026-13187?
- CVE-2026-13187 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2026-13187 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-13187?
- CVE-2026-13187 affects Progress Telerik Ui For Asp.net Ajax. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-13187?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2026-13187 published?
- CVE-2026-13187 was published on 2026-07-22 and last updated on 2026-08-06.
References
Affected products (1)
- cpe:2.3:a:progress:telerik_ui_for_asp.net_ajax:*:*:*:*:*:*:*:*
More vulnerabilities in Progress Telerik Ui For Asp.net Ajax
- CVE-2021-28141 — Critical (CVSS 9.8): An issue was discovered in Progress Telerik UI for ASP.NET AJAX 2021.1.224. It allows unauthorized access to…
- CVE-2019-19790 — Critical (CVSS 9.8): Path traversal in RadChart in Telerik UI for ASP.NET AJAX allows a remote attacker to read and delete an image with…
- CVE-2017-11357 — Critical (CVSS 9.8): Progress Telerik UI for ASP.NET AJAX before R2 2017 SP2 does not properly restrict user input to RadAsyncUpload, which…
- CVE-2026-13190 — High (CVSS 8.1): In Progress® Telerik® UI for AJAX prior to v2026.2.708, a deserialization vulnerability in the persistence utilities…
- CVE-2026-13186 — High (CVSS 8.1): In Progress® Telerik® UI for AJAX prior to v2026.2.708, a path traversal vulnerability in the file-based persistence…
- CVE-2026-13185 — High (CVSS 8.1): In Progress® Telerik® UI for AJAX prior to v2026.2.708, applications using cookie-based storage in…
All CVEs affecting Progress Telerik Ui For Asp.net Ajax →
Other CWE-470 (Unsafe Reflection) vulnerabilities
- CVE-2026-40008 — Critical (CVSS 9.8): Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Apache IoTDB. The…
- CVE-2026-42027 — Critical (CVSS 9.8): Arbitrary Class Instantiation via Model Manifest in Apache OpenNLP ExtensionLoader Versions Affected: before…
- CVE-2025-34393 — Critical (CVSS 9.8): Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, does not correctly verify…
- CVE-2025-53693 — Critical (CVSS 9.8): Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Sitecore Sitecore…
- CVE-2023-6943 — Critical (CVSS 9.8): Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Mitsubishi Electric…
- CVE-2021-31522 — Critical (CVSS 9.8): Kylin can receive user input and load any class through Class.forName(...). This issue affects Apache Kylin 2 version…