Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Odin Research / What is / Targeted enterprise software

What Is Telerik UI? Telerik UI for ASP.NET AJAX Vulnerabilities Explained

A widely embedded web component library whose upload handler has been a favorite entry point for years. The CVEs that matter and how to close them.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
7 min read
Type
Enterprise software (web UI library)

In short

Telerik UI for ASP.NET AJAX is a commercial library of more than 120 web components from Progress, used to build ASP.NET Web Forms applications. Its RadAsyncUpload file-upload handler has had several serious flaws, including CVE-2019-18935, which CISA lists as exploited. Attackers use these flaws to gain code execution on IIS web servers.

Key takeaways

What it is
A Progress Telerik component library for ASP.NET Web Forms, with more than 120 components, often buried inside custom and third-party web apps.
Why it is a target
Its RadAsyncUpload handler has a long CVE history. CVE-2019-18935, CVE-2017-11317 and CVE-2017-9248 are all in CISA's Known Exploited Vulnerabilities catalog.
Newest flaws
CVE-2026-13182 (an error oracle) and CVE-2026-13181 (forged upload metadata) affect versions before 2026.2.708.
What Odin Research saw
An exposed staging server with 25 padding-oracle and assembly scripts and a local Telerik lab, citing the 2026 advisories and building on CVE-2019-18935.
What to do first
Find every Telerik.Web.UI copy on your servers, upgrade to 2026.2.708 or later, and disable the upload handler where you do not need it.

What is Telerik UI?

Telerik UI for ASP.NET AJAX is a commercial component library from Progress for building ASP.NET Web Forms applications. Progress describes it as a mature library with more than 120 components, such as grids, editors and upload controls. Developers drop these components into web pages instead of writing them from scratch.

The library ships as an assembly, Telerik.Web.UI.dll, inside the application. That is the security problem. Many organizations run Telerik without knowing it, because it is buried inside a custom app or a third-party product. Old copies stay in place long after the app is forgotten.

Telerik is a brand with several UI products. This page covers Telerik UI for ASP.NET AJAX, the product behind the CVEs below.

Attackers care most about one component: RadAsyncUpload, the asynchronous file upload handler. It has been the root of several critical flaws, and those flaws have been used against real government servers.

How Telerik UI RadAsyncUpload flaws work

RadAsyncUpload accepts uploads in the background. To keep track of each upload, it passes encrypted metadata between the browser and the server. Most Telerik flaws come down to that metadata.

  • Weak or known keys. If an attacker can forge or decrypt the metadata, they can tell the server what to do with an upload. CVE-2017-11317 describes weak RadAsyncUpload encryption that allows arbitrary file uploads or code execution.
  • Deserialization. CVE-2019-18935 is a .NET deserialization flaw in RadAsyncUpload. With known encryption keys, an attacker can achieve remote code execution.
  • Error oracles. CVE-2026-13182 lets attackers tell decryption failures apart from invalid-JSON failures. That difference acts as an oracle that can reveal protected metadata.

The pattern repeats: break or learn the protection on the upload metadata, then use it to plant a file or trigger code. The end state is usually a web shell on the IIS server.

Telerik UI CVEs defenders should know

All details below were checked on NVD on 21 November 2026.

  • CVE-2017-9248: Telerik.Web.UI.dll before R2 2017 SP1 does not properly protect its dialog parameters encryption key. This can lead to a MachineKey leak, file uploads or downloads and ViewState attacks. CVSS 3.1 score 9.8. Added to CISA KEV on 3 November 2021.
  • CVE-2017-11317: weak RadAsyncUpload encryption before R1 2017 and R2 2017 SP2. CVSS 9.8. Added to KEV on 11 April 2022.
  • CVE-2019-18935: RadAsyncUpload deserialization in versions through 2019.3.1023. NVD notes that a default setting prevents exploitation as of 2020.1.114. CVSS 9.8. Added to KEV on 3 November 2021.
  • CVE-2026-13181: forged upload metadata in versions before 2026.2.708 can influence type resolution, potentially enabling remote code execution. CVSS 8.1.
  • CVE-2026-13182: the RadAsyncUpload error oracle, published on 22 July 2026. CVSS 7.5. Progress lists versions 2010.1.309 to 2026.2.519 as affected and 2026.2.708 (2026 Q2 SP1) as fixed.

Three of these are in the Known Exploited Vulnerabilities catalog. NVD did not show a KEV entry for CVE-2026-13182 when we checked.

How attackers use Telerik UI flaws

Telerik flaws are a classic route to Exploit Public-Facing Application (T1190).

CISA, the FBI and MS-ISAC described the best-known case in advisory AA23-074A. From November 2022 through early January 2023, they found indicators of intrusion at a US federal civilian executive branch agency. Multiple threat actors, including an APT actor and the cybercriminal XE Group, had exploited CVE-2019-18935 on the agency's IIS web server.

The detail that matters most: the agency's vulnerability scanner had the right plugin but missed the flaw. Telerik was installed in a file path the scanner did not normally check.

A June 2023 update added a second agency. In April 2023, unidentified APT actors had used the older CVE-2017-9248 against an outdated Telerik version, gaining web shell access and keeping persistence.

The lesson is that Telerik risk is an inventory problem as much as a patching one. You cannot patch the copy you do not know about.

What Odin Research observed

Monograph 01 analyzed an exposed staging server holding 364 attack files. Together they lay out a path from a perimeter web application through internal databases to the domain controller and the VMware hypervisor layer.

  • A local Telerik lab. The server's root folder held 38 numbered files outside the project folders. 25 of them, 23 Python and 2 PowerShell scripts, are padding-oracle and assembly-patching scripts. The other 13 are local lab files.
  • Current advisories. Script headers cite the 2026 Telerik UI for ASP.NET AJAX advisories, including CVE-2026-13182, and build on the older CVE-2019-18935. One script tests the CVE-2026-13182 padding and JSON-parse error difference.
  • Native code loading. Another script builds a mixed-mode .NET assembly that can load native code.
  • Lab, not target. The scripts point at a local IIS lab. None names the perimeter target. Odin Research notes the lab may have been used to test a payload before delivery, or may be separate research on a shared server.

The wider playbook's entry stage is a web shell on a Windows GIS web server. Later stages pivot through SQL Server with xp_cmdshell, attempt DCSync and probe VMware ESXi. Odin found no record that any of these steps worked.

How to detect Telerik UI exploitation

  • Find every copy. Search all web servers for Telerik.Web.UI.dll and record its version. Include third-party apps and unusual install paths, the gap CISA described.
  • Watch the upload handler. Bursts of requests to the RadAsyncUpload handler with varying encrypted metadata and error responses suggest oracle or key-guessing attempts.
  • New files in upload folders. Unexpected DLLs or scripts in upload, temp or App_Data folders deserve a look.
  • IIS worker children. w3wp.exe starting cmd.exe, PowerShell or certutil.exe is a strong post-exploitation signal.
  • Unexpected outbound traffic. CISA advises monitoring for unexpected outbound connections from web servers.

Monograph 01 does not carry a Telerik-specific rule. Its Sigma, YARA and Suricata rules cover what comes next: web workers spawning chunked PowerShell stagers, minimal web shells and the staging markers the playbook uses. The report also recommends scanning web upload folders and App_Data with its YARA rules. All are in the Defense Kit.

How to defend Telerik UI applications

  1. Upgrade. Move internet-facing Telerik UI for ASP.NET AJAX to 2026.2.708 or later, as Progress and Monograph 01 recommend.
  2. Apply the vendor workarounds if you cannot upgrade yet. Progress lists removing custom Telerik encryption keys from web.config to fall back on machineKey, generating strong HMACSHA256 machine keys with auto-generation disabled, and setting customErrors to On or RemoteOnly.
  3. Disable the upload handler if unused. Progress documents a Telerik.Web.DisableAsyncUploadHandler setting for applications that do not need it.
  4. Fix your scanner coverage. Configure scanners to check all install paths, as CISA advises.
  5. Limit the blast radius. Run IIS application pools with minimal rights and segment web servers from databases and domain controllers. See our guide to responding to actively exploited vulnerabilities.

Telerik UI flaws compared with other web entry points

FlawProductTypeCVSS 3.1
CVE-2019-18935Telerik UI for ASP.NET AJAXDeserialization in RadAsyncUpload9.8
CVE-2026-13182Telerik UI for ASP.NET AJAXError oracle in RadAsyncUpload7.5
Log4Shell (CVE-2021-44228)Apache Log4j2JNDI lookup in logged input10.0
Ghostcat (CVE-2020-1938)Apache Tomcat AJPAJP connector file read and inclusion9.8

Monograph 01's playbook touches several of these: it builds on Telerik flaws and holds two Log4Shell probes the operator gave up on.

Frequently asked questions about Telerik UI

What is Telerik UI?

Telerik UI for ASP.NET AJAX is a commercial library of more than 120 web components from Progress, used to build ASP.NET Web Forms applications. It ships as Telerik.Web.UI.dll inside the application.

Is Telerik UI vulnerable?

Older versions have several serious flaws, mostly in the RadAsyncUpload component. CVE-2019-18935, CVE-2017-11317 and CVE-2017-9248 are in CISA's Known Exploited Vulnerabilities catalog, and CVE-2026-13181 and CVE-2026-13182 affect versions before 2026.2.708.

What is CVE-2019-18935?

CVE-2019-18935 is a .NET deserialization flaw in the RadAsyncUpload function of Telerik UI for ASP.NET AJAX through 2019.3.1023. With known encryption keys, attackers can achieve remote code execution. NVD scores it 9.8.

What is CVE-2026-13182?

It is a flaw in Telerik UI for ASP.NET AJAX before 2026.2.708. RadAsyncUpload lets attackers tell decryption failures from invalid-JSON failures, creating an oracle that can reveal protected metadata. NVD scores it 7.5.

Which Telerik version fixes the 2026 flaws?

Progress lists 2026.2.708 (2026 Q2 SP1) as the fixed version for CVE-2026-13182, with versions 2010.1.309 to 2026.2.519 affected.

How do I find Telerik in my environment?

Search every web server for Telerik.Web.UI.dll and check its version, including third-party products and non-standard install paths. CISA found that a scanner missed a vulnerable copy because of its install path.

How do I detect Telerik exploitation?

Watch for bursts of requests to the RadAsyncUpload handler, new files in upload folders, IIS worker processes starting shells and unexpected outbound connections from web servers.

Who has exploited Telerik vulnerabilities?

CISA advisory AA23-074A reports that multiple actors, including an APT actor and the XE Group, exploited CVE-2019-18935 at a US federal agency between November 2022 and January 2023.

Sources

  1. Progress, Telerik UI for ASP.NET AJAX product page. www.telerik.com/products/aspnet-ajax.aspx (checked 21 November 2026)
  2. Progress Telerik, Cryptographic oracle vulnerability in RadAsyncUpload (CVE-2026-13182). www.telerik.com/products/aspnet-ajax/documentation/knowledge-base/kb-security-rau-padding-oracle-cve-2026-13182 (checked 21 November 2026)
  3. NVD, CVE-2026-13182. nvd.nist.gov/vuln/detail/CVE-2026-13182 (checked 21 November 2026)
  4. NVD, CVE-2026-13181. nvd.nist.gov/vuln/detail/CVE-2026-13181 (checked 21 November 2026)
  5. NVD, CVE-2019-18935. nvd.nist.gov/vuln/detail/CVE-2019-18935 (checked 21 November 2026)
  6. NVD, CVE-2017-11317. nvd.nist.gov/vuln/detail/CVE-2017-11317 (checked 21 November 2026)
  7. NVD, CVE-2017-9248. nvd.nist.gov/vuln/detail/CVE-2017-9248 (checked 21 November 2026)
  8. CISA, FBI and MS-ISAC, AA23-074A, "Threat Actors Exploit Progress Telerik Vulnerabilities in Multiple U.S. Government IIS Servers". www.cisa.gov/news-events/cybersecurity-advisories/aa23-074a (checked 21 November 2026)
  9. NVD, CVE-2021-44228. nvd.nist.gov/vuln/detail/CVE-2021-44228 (checked 21 November 2026)
  10. NVD, CVE-2020-1938. nvd.nist.gov/vuln/detail/CVE-2020-1938 (checked 21 November 2026)
  11. MITRE ATT&CK, Exploit Public-Facing Application, T1190. attack.mitre.org/techniques/T1190/ (checked 21 November 2026)

Related tools and terms

All Odin Research explanations · Brandefense glossary

Odin Research

Get the rules, not just the definition

Every Odin Research report ships with verified indicators and detection rules you can load today.

Open the Defense Kit