Skip to content

Vendor

Progress Software vulnerabilities

304 published CVES affecting Progress Software, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
304
Critical
44
High
175
Medium
84
Low
1
Unscored
0
CISA KEV
6
Atom feed of Progress Software alerts

Products

Latest Progress Software CVEs

Newest publication first · page 1 of 13

  1. HighCVSS 7.8 EPSS 0.11%

    In Telerik UI for WPF, versions prior to 2026.4.1110, 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-allowlisted UR...

  2. HighCVSS 7.1 EPSS 0.15%

    In Progress Kendo UI for jQuery, the Chart default tooltip renders point values as raw HTML. An attacker who can influence a string point value can inject markup that executes as JavaScript when a user hovers over the point. Successful exploitation may compromise the confidential...

  3. HighCVSS 7.1 EPSS 0.15%

    In Progress Kendo UI for jQuery, Chart shared-tooltip rendering treats bound category and series-name values as raw HTML. An attacker who can influence values consumed by an affected Chart can inject markup that executes as JavaScript when a user displays the shared tooltip. Succ...

  4. HighCVSS 7.1 EPSS 0.15%

    In Progress Kendo UI for jQuery Form, the items[].hint option is documented as a string but is rendered as HTML. An attacker who can influence a Form item's hint can cause attacker-controlled markup to execute as JavaScript when a user views the rendered form. Successful exploita...

  5. HighCVSS 7.1 EPSS 0.19%

    In Progress Kendo UI for jQuery versions 2026.3.1015 up to, but not including, 2026.4.1110, PivotGrid and PivotConfigurator axis field names are passed to a chip template without appropriate encoding. An attacker who can influence an axis field name can cause JavaScript to execut...

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.