In Telerik UI for WinForms, versions prior to 2026.4.1111, an untrusted URL redirection vulnerability exists that allows an attacker to launch arbitrary operating system protocol handlers with attacker-controlled arguments via crafted documents and hyperlinks with a non-allowlist...
Product
Progress Software Telerik UI for WinForms vulnerabilities
6 published CVES affecting Progress Software Telerik UI for WinForms, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 5
- Medium
- 1
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest Progress Software Telerik UI for WinForms CVEs
Newest publication first
-
HighCVSS 7.8
-
HighCVSS 7.8
In Telerik UI for WinForms, versions prior to 2026.4.1111, a deserialization of untrusted data vulnerability exists that allows an attacker to perform unauthorized actions in the context of the affected application.
-
CVE-2026-124699 Improper Control of Generation of Code in Progress Telerik UI for WinForms
PublishedHighCVSS 7.8 EPSS 0.19%In Telerik UI for WinForms, versions prior to 2026.4.1111, an improper control of code generation vulnerability exists that allows an attacker to supply a crafted expression and execute unauthorized code in the context of the affected application.
-
CVE-2024-10013 Progress UI for WinForms format provider unsafe deserialization vulnerability
PublishedHighCVSS 7.8 EPSS 0.22%In Progress Telerik UI for WinForms versions prior to 2024 Q4 (2024.4.1113), a code execution attack is possible through an insecure deserialization vulnerability.
-
HighCVSS 7.8 EPSS 0.74%
In Progress Telerik UI for WinForms versions prior to 2024 Q3 (2024.3.924), a command injection attack is possible through improper neutralization of hyperlink elements.
-
MediumCVSS 6.7 EPSS 0.22%
A local code execution vulnerability is possible in Telerik UI for WinForms beginning in v2021.1.122 but prior to v2024.2.514. This vulnerability could allow an untrusted theme assembly to execute arbitrary code on the local Windows system.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.