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

New CVE Detected

CVE-2026-13186 – Path Traversal to RCE – Telerik UI for ASP.NET AJAX prior to v2026.2.708

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

Summary

CVE-2026-13186 is a path traversal vulnerability (CWE-22) in the file-based persistence storage provider of Progress Telerik UI for ASP.NET AJAX, affecting versions 2013.1.220 through 2026.2.519 (all releases prior to 2026.2.708). When the RadPersistenceManager component’s storage key is derived from user-controlled input, an unauthenticated remote attacker can manipulate the file path used to load persistence state, triggering attacker-controlled deserialization and achieving remote code execution (RCE) on the underlying server. The vulnerability carries a CVSS v3.1 base score of 8.1 (High).

Technical details

  • Root cause: The RadPersistenceManager component, when configured with a file-based storage provider, does not adequately restrict the pathname used to resolve the persistence state file. If the storage key is derived from user-controlled sources — such as query parameters, form fields, or cookies — an attacker can craft input containing path traversal sequences to influence which file on the server is loaded and deserialized.
  • Trigger conditions: Exploitation requires the application to use RadPersistenceManager with a file-based storage provider and a storage key sourced from attacker-controlled input. Applications that rely exclusively on server-side state to derive storage keys are not affected by this vulnerability.
  • Attack vector: Network-accessible and unauthenticated — no privileges or user interaction are required. Attack complexity is rated High (AC:H) because the vulnerable configuration (file-based storage with user-controlled keys) is non-default; however, it is a documented and used deployment pattern.
  • Impact: Successful exploitation allows the attacker to control which file the application deserializes, enabling arbitrary code execution on the server. Full compromise of confidentiality, integrity, and availability is possible. The attack potential is further increased when the attacker also has file upload capability within the server’s App_Data directory.

Affected software

  • Progress Telerik UI for ASP.NET AJAX — versions 2013.1.220 through 2026.2.519 (all versions prior to 2026.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: Upgrade to Progress Telerik UI for ASP.NET AJAX version 2026.2.708 (2026 Q2 SP1) or later, which contains the vendor-provided fix.
  • Workaround (if immediate upgrade is not feasible):
    • Ensure the RadPersistenceManager storage key is derived exclusively from server-side state — never from query parameters, form fields, or cookies.
    • As an additional defense-in-depth measure, relocate the RadAsyncUpload temporary folder outside the App_Data directory by configuring the Telerik.AsyncUpload.TemporaryFolder application setting. Note: this measure alone does not substitute for the primary mitigation above.

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