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

New CVE Detected

CVE-2026-13185 – Unauthenticated RCE via Cookie Deserialization – Telerik UI for ASP.NET AJAX pri…

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

Summary

CVE-2026-13185 is a high-severity insecure deserialization vulnerability (CWE-502) in Progress Telerik UI for ASP.NET AJAX affecting all versions from 2013.1.220 up to and including 2026.2.519. When an application uses cookie-based state storage in the RadPersistenceManager or RadDockLayout components, attacker-controlled cookie content is deserialized without sufficient validation, enabling unauthenticated remote code execution (RCE) on the server. Progress Software has released a fix in version 2026.2.708 (Q2 SP1).

Technical details

  • Root cause: Deserialization of untrusted data (CWE-502) — the affected components deserialize cookie values directly from client-supplied HTTP cookies without adequate validation or integrity verification.
  • Trigger conditions: The vulnerability is only reachable when an application has explicitly configured cookie-based state persistence: RadPersistenceManager using CookieStateStorageProvider, or RadDockLayout with LayoutPersistenceRepositoryType set to Cookies. These are non-default but supported configurations present in real-world deployments.
  • Attack vector: An unauthenticated remote attacker submits a crafted HTTP request carrying a malicious serialized payload in the relevant cookie. No user interaction and no prior authentication are required.
  • Impact: Successful exploitation achieves full remote code execution on the server, resulting in complete compromise of confidentiality, integrity, and availability (C:H/I:H/A:H).

Affected software

  • Progress Telerik UI for ASP.NET AJAX versions 2013.1.220 through 2026.2.519 (all releases prior to 2026.2.708)

Severity

CVSS v3.1 Base Score: 8.1 (HIGH)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate (recommended): Upgrade to Telerik UI for ASP.NET AJAX v2026.2.708 (2026 Q2 SP1) or later, which contains the vendor-provided fix.
  • Interim workarounds (if immediate patching is not possible):
    • Do not configure RadPersistenceManager with CookieStateStorageProvider. Switch to server-side, database, or session-based persistence instead.
    • Ensure RadDockLayout does not use cookie-based persistence (LayoutPersistenceRepositoryType should not be set to Cookies).

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge