Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-13190 – RCE via Deserialization – Progress Telerik UI for ASP.NET AJAX prior to v2026.2.708

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

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 RadPersistenceManager component 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) RadPersistenceManager is 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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge