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

New CVE Detected

CVE-2026-13183 – Cryptographic Timing Oracle Exposes Protected Metadata – Progress Telerik UI for…

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

Summary

CVE-2026-13183 is a high-severity cryptographic timing oracle vulnerability in the RadAsyncUpload component of Progress Telerik UI for ASP.NET AJAX, affecting all versions from 2010.1.309 through 2026.2.707. By exploiting measurable timing differences during upload metadata processing, an unauthenticated remote attacker can recover cryptographically protected metadata values, resulting in high confidentiality impact (CVSS 7.5). Progress has released a fix in version 2026.2.708 (2026 Q2 SP1).

Technical details

  • Root cause: The RadAsyncUpload component’s metadata processing routine leaks cryptographic validity through observable differences in server response timing (CWE-208: Observable Timing Discrepancy / CAPEC-385: Covert Timing Channel). These timing variations allow an attacker to distinguish valid from invalid cryptographic metadata, functioning as a timing oracle.
  • Trigger conditions: An attacker submits crafted upload requests to the RadAsyncUpload HTTP handler. Differences in server processing time depending on cryptographic validation outcomes disclose information about the protected metadata’s validity, enabling iterative recovery of its values.
  • Attack vector: Network-accessible with no authentication and no user interaction required (AV:N/AC:L/PR:N/UI:N). The RadAsyncUpload handler is exposed over standard HTTP/HTTPS on ASP.NET applications hosted on IIS.
  • Impact: High confidentiality impact — an attacker can recover cryptographically protected upload metadata. Recovery of RadAsyncUpload metadata values is a known precursor to more severe exploitation: previous vulnerabilities in the same component demonstrated that weaknesses in its cryptographic metadata handling could be leveraged for deserialization-based remote code execution.

Affected software

  • Progress Telerik UI for ASP.NET AJAX versions 2010.1.309 through 2026.2.707 (all versions prior to v2026.2.708)

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: Upgrade to Progress Telerik UI for ASP.NET AJAX version 2026.2.708 (2026 Q2 SP1) or later. This release introduces AES-GCM encryption to address the timing oracle in metadata processing.
  • If immediate upgrade is not feasible:
    • If RadAsyncUpload is not required by the application, disable its HTTP handler entirely by setting Telerik.Web.DisableAsyncUploadHandler to true in web.config.
    • For deployments using custom encryption keys, remove custom key configurations from web.config to revert metadata protection to MachineKey.Unprotect (AES + HMAC), and configure strong, non-auto-generated machine keys via IIS Manager (set validation to HMACSHA256, disable "automatically generate at runtime", and recycle the application pool after applying keys).

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