Skip to content
Web

CVE-2026-13190

8.1
High
EPSS 0.67%Patch availableJul 23, 2026

Unsafe deserialization in Telerik UI for AJAX allows remote code execution.

common questions

Is CVE-2026-13190 being exploited?

Not confirmed. CVE-2026-13190 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.67% probability of exploitation in the next 30 days.

How severe is CVE-2026-13190?

CVE-2026-13190 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-13190?

Yes. A fix has been recorded for CVE-2026-13190. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-13190 affect?

CVE-2026-13190 affects Progress Telerik UI for ASP.NET AJAX < v2026.2.708, Applications using Telerik AJAX persistence utilities. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-13190?

Upgrade to v2026.2.708+; block/validate persisted state endpoints if patch delayed

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Progress Telerik UI for ASP.NET AJAX < v2026.2.708Applications using Telerik AJAX persistence utilities
impact

Remote code execution via unsafe deserialization of attacker-controlled persisted state, enabling arbitrary code execution on affected servers.

action required

Immediate action required

affected versions
Progress Software Telerik UI for ASP.NET AJAX
  • affected>= 2011.2.712 and < 2026.2.708

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free