CVE-2026-13181: RadAsyncUpload AsyncUploadTypeName Type Resolution Vulnerability in Telerik UI for ASP.NET AJAX
In Progress® Telerik® UI for AJAX prior to v2026.2.708, forged upload metadata can influence AsyncUploadTypeName processing and trigger unsafe attacker-controlled type resolution, enabling remote code execution in affected deployments.
Security readout for executives and security teams
Plain-English summary
Affected Telerik web applications may allow an unauthenticated remote attacker to turn forged upload information into server-side code execution. Successful exploitation could expose data, alter applications, or disrupt services. Exploitation requires higher complexity, but no user interaction or existing account is required.
Executive priority
Treat as a high-priority remediation for internet-facing systems. Establish exposure immediately and upgrade affected deployments promptly. The remote-code-execution impact is severe, although high attack complexity and no confirmed active exploitation reduce the case for emergency shutdown absent additional evidence.
Technical view
RadAsyncUpload can process forged metadata that influences AsyncUploadTypeName and causes unsafe attacker-controlled type resolution. The issue is classified as CWE-470 and may enable remote code execution. CVSS 3.1 is 8.1: network-accessible, unauthenticated, high complexity, no user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Likely exposure exists where Telerik UI for ASP.NET AJAX before v2026.2.708 processes reachable RadAsyncUpload requests. However, the structured affected entry explicitly lists 2010.1.309 and otherwise defaults to unaffected, conflicting with the broader narrative. Confirm exact version scope through the vendor advisory.
Exploitation context
The supplied sources do not establish active exploitation, and this CVE is not identified as KEV. The attack is remotely reachable without authentication or user interaction, but rated high complexity. No exploit method or prerequisite configuration beyond affected RadAsyncUpload processing is documented in the bundle.
Researcher notes
Version evidence requires caution: the description covers releases before v2026.2.708, while the structured affected data lists only 2010.1.309 and defaults others to unaffected. Researchers should preserve that uncertainty. The bundle supports unsafe type resolution and potential remote code execution, but provides no evidence of public exploitation or specific attack prerequisites.
Mitigation direction
Upgrade Telerik UI for ASP.NET AJAX to v2026.2.708 or later.
Confirm supported remediation and affected-version details in the vendor advisory.
Prioritize internet-facing applications that expose RadAsyncUpload functionality.
Restrict unnecessary external access while remediation is pending.
Validation and detection
Inventory Telerik UI for ASP.NET AJAX versions across deployed applications.
Identify applications using RadAsyncUpload and determine whether upload routes are externally reachable.
Verify deployed Telerik components report v2026.2.708 or later after remediation.
Review upload-related telemetry for unexpected metadata or abnormal application behavior.
Recheck vendor guidance because the supplied version records are internally inconsistent.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-470: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-470 · source CWE mapping
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.