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

New CVE Detected

CVE-2026-13182 – Decryption Oracle in RadAsyncUpload – Telerik UI for ASP.NET AJAX prior to v2026…

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

Summary

CVE-2026-13182 is a high-severity cryptographic (padding) oracle vulnerability in the RadAsyncUpload component of Progress Telerik UI for ASP.NET AJAX. The flaw affects all versions from 2010.1.309 through 2026.2.519, and allows unauthenticated remote attackers to progressively recover protected metadata values by exploiting the component’s differentiated error responses during client-state processing. The vulnerability carries a CVSS v3.1 base score of 7.5 (High).

Technical details

  • Root cause: The RadAsyncUpload component’s client-state processing returns distinguishable responses depending on whether a submitted payload triggers a decryption failure or an invalid-JSON parse failure (CWE-209: Generation of Error Message Containing Sensitive Information). This behavioral difference constitutes a classic cryptographic oracle (CAPEC-463: Padding Oracle Crypto Attack).
  • Trigger condition: An attacker submits crafted client-state payloads to the RadAsyncUpload HTTP handler endpoint (accessible via the Telerik.Web.UI.WebResource.axd handler with type=rau). By iterating over malformed ciphertext blocks and observing differing server responses, the attacker can deduce plaintext content one block at a time — without needing to know the application’s encryption keys.
  • Attack vector: Network-reachable, no authentication required, no user interaction required, low attack complexity. The handler is exposed as a public HTTP endpoint on any application that uses RadAsyncUpload.
  • Impact: High confidentiality impact — protected metadata values embedded in encrypted client state are recoverable. Historically, recovering such metadata from RadAsyncUpload has enabled chaining into .NET deserialization attacks leading to remote code execution, as documented by CISA in advisory AA23-074A in the context of CVE-2019-18935 and CVE-2017-11317.

Affected software

  • Progress Telerik UI for ASP.NET AJAX versions 2010.1.309 through 2026.2.519 (all releases up to and including the 2026 Q2 base release)

Severity

CVSS v3.1 Base Score: 7.5 (High)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate — apply the vendor patch: Upgrade to Telerik UI for ASP.NET AJAX version 2026.2.708 (2026 Q2 SP1) or later. Version 2026.2.708 introduces AES-GCM authenticated encryption for RadAsyncUpload client state, which is not vulnerable to padding oracle attacks.
  • If immediate patching is not feasible — apply vendor-recommended workarounds:
    • Remove custom Telerik.AsyncUpload.ConfigurationEncryptionKey and Telerik.Upload.ConfigurationHashKey values from web.config so the component falls back to MachineKey.Unprotect (AES + HMAC), eliminating the oracle differential.
    • Generate and configure strong machine keys in IIS using HMACSHA256 validation to harden the fallback path.
    • Set ASP.NET customErrors to "On" or "RemoteOnly" to suppress differentiated error responses visible to remote clients.
    • If RadAsyncUpload is not actively used by the application, disable the handler entirely by setting the application setting Telerik.Web.DisableAsyncUploadHandler to true in web.config.

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