Summary
CVE-2026-13190 is a high-severity deserialization vulnerability (CWE-502) in the PersistenceFramework component of Progress® Telerik® UI for ASP.NET AJAX, affecting all versions from 2011.2.712 up to and including 2026.2.519 (prior to v2026.2.708). An unauthenticated network-based attacker who can influence persisted state — for example, via a client-accessible cookie or writable storage location — can trigger unsafe type instantiation during deserialization, leading to Remote Code Execution on the host server. The CVSS 3.1 base score is 8.1 (High).
Technical details
- Root cause: The
RadPersistenceManagercomponent deserializes persisted state data without sufficient validation of the types being instantiated, classified as CWE-502 (Deserialization of Untrusted Data) / CAPEC-586 (Object Injection). - Trigger conditions: The vulnerability is exploitable when (1)
RadPersistenceManageris actively used by the application, and (2) an attacker can modify the persisted state — for example, because it is stored in a client-accessible location such as an HTTP cookie, or because persistence storage files are writable by untrusted users. - Attack vector: Network (AV:N), no authentication required (PR:N), no user interaction required (UI:N); attack complexity is rated High (AC:H) reflecting the requirement that persistence state must be exposed to attacker influence.
- Impact: Successful exploitation leads to arbitrary remote code execution with full server-side impact — complete compromise of confidentiality, integrity, and availability (C:H/I:H/A:H).
Affected software
- Progress® Telerik® UI for ASP.NET AJAX — versions 2011.2.712 through 2026.2.519 (all releases prior to v2026.2.708)
Severity
- CVSS v3.1 Base Score: 8.1 (High)
- Vector String:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate – apply the vendor patch: Upgrade to v2026.2.708 (2026 Q2 SP1) or later, which resolves the unsafe type instantiation in the PersistenceFramework.
- If immediate patching is not possible:
- Restrict write access to persistence storage directories so that unauthenticated or untrusted users cannot modify persisted state files.
- Do not derive the persistence storage key from attacker-controllable request data; use fixed, hardcoded values instead of user-supplied input.
- Avoid using client-side storage providers (e.g.,
CookieStateStorageProvider) for persistence state in externally accessible applications until the patch is applied.
IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

