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

New CVE Detected

CVE-2026-13181 – Remote Code Execution via Unsafe Type Resolution – Progress Telerik UI for ASP.N…

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

Summary

CVE-2026-13181 is a high-severity vulnerability in Progress Telerik UI for ASP.NET AJAX affecting all versions from 2010.1.309 through 2026.2.519, fixed in v2026.2.708. The flaw arises from the RadAsyncUpload component resolving server-side .NET types from attacker-controlled upload metadata — specifically the AsyncUploadTypeName parameter — without adequate validation, enabling unauthenticated remote code execution. The vulnerability is classified under CWE-470 (Use of Externally-Controlled Input to Select Classes or Code) and carries a CVSS v3.1 base score of 8.1 (HIGH).

Technical details

  • Root cause: The RadAsyncUpload handler (Telerik.Web.UI.WebResource.axd) processes type names supplied within forged upload metadata. The AsyncUploadTypeName field is resolved to a .NET type without sufficient validation, enabling an attacker to influence object instantiation on the server — an object injection pattern classified as CWE-470 / CAPEC-586.
  • Trigger conditions: The application must have the RadAsyncUpload control in active use and the async upload handler must not have been explicitly disabled via the Telerik.Web.DisableAsyncUploadHandler configuration key.
  • Attack vector: Network-delivered over HTTP/HTTPS; no authentication required, no user interaction required. The handler endpoint is accessible to unauthenticated internet users on affected deployments.
  • Impact: Full remote code execution on the server — confidentiality, integrity, and availability are all rated HIGH (C:H/I:H/A:H). Successful exploitation can result in complete server compromise.

Affected software

  • Progress Telerik UI for ASP.NET AJAX versions 2010.1.309 through 2026.2.519 (inclusive) — all versions prior to the 2026 Q2 SP1 release

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

Note: The High Attack Complexity (AC:H) reflects the prerequisite that RadAsyncUpload must be actively configured in the application. It does not reduce severity for environments meeting that condition.

Mitigation and recommended actions

  • Immediate — upgrade: Apply Progress Telerik UI for ASP.NET AJAX v2026.2.708 (2026 Q2 SP1) or later. This release addresses the unsafe type resolution in AsyncUploadTypeName handling.
  • If immediate upgrade is not feasible — workarounds:
    • Disable the async upload handler entirely by setting Telerik.Web.DisableAsyncUploadHandler to true in web.config. This blocks the vulnerable code path if RadAsyncUpload functionality is not required.
    • Configure strong, manually generated machine keys in IIS using HMACSHA256 validation to reduce the effectiveness of forged metadata. Do not rely on auto-generated keys.
    • Review and restrict network access to the Telerik.Web.UI.WebResource.axd handler endpoint where possible.

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