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

New CVE Detected

CVE-2026-13184 – Upload Integrity Bypass via Predictable HMAC Key Fallback – Telerik UI for ASP.N…

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

Summary

CVE-2026-13184 is a high-severity upload metadata integrity bypass vulnerability (CVSS 7.5) affecting Progress® Telerik® UI for ASP.NET AJAX versions 2010.1.309 through 2026.2.519. When Telerik.Upload.ConfigurationHashKey is absent and machineKey is not explicitly configured in the application, the RadAsyncUpload component’s integrity protection falls back to a predictable default HMAC key (CWE-321), allowing unauthenticated remote attackers to forge protected upload metadata and unlock further exploit chains. No authentication, privileges, or user interaction are required.

Technical details

  • Root cause: The RadAsyncUpload handler implements an Encrypt-then-MAC scheme to protect upload metadata integrity via Telerik.Upload.ConfigurationHashKey. When this key is absent and ASP.NET’s machineKey is left on its default auto-generated setting, the handler falls back to a predictable hard-coded HMAC key (CWE-321) instead of a securely derived key, nullifying the integrity check.
  • Trigger conditions: Two conditions must both be true — (1) Telerik.Upload.ConfigurationHashKey is not explicitly set in web.config, and (2) machineKey is configured to auto-generate at runtime (the ASP.NET default) or is otherwise absent from web.config.
  • Attack vector: Network-accessible, unauthenticated HTTP/HTTPS requests to the RadAsyncUpload handler. No privileges and no user interaction are required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N).
  • Impact: An attacker who knows or can reproduce the predictable default key can craft forged upload metadata that passes the server-side HMAC integrity check. The vendor describes this as enabling "further exploit chains" — consistent with the historical pattern for this class of Telerik upload key exposure, where metadata forgery has served as a precursor to arbitrary file upload and remote code execution.

Affected software

  • Progress® Telerik® UI for ASP.NET AJAX — versions 2010.1.309 through 2026.2.519 (all versions prior to 2026.2.708)

Severity

  • CVSS v3.1 Base Score: 7.5 (High)
  • Vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
  • CWE: CWE-321 – Use of Hard-coded Cryptographic Key

Mitigation and recommended actions

  • Immediate — apply the vendor patch: Upgrade to Telerik UI for ASP.NET AJAX v2026.2.708 (2026 Q2 SP1) or later, which removes the predictable fallback key behavior.
  • Workaround option 1 (if patching is not immediately possible): Remove the Telerik.AsyncUpload.ConfigurationEncryptionKey entry from web.config. This forces the upload handler to use ASP.NET’s MachineKey.Unprotect rather than the vulnerable fallback path.
  • Workaround option 2: Explicitly configure a strong, unique machine key in IIS — disable the "automatically generate at runtime" option and use the IIS Machine Key interface to generate and apply a static key with HMACSHA256 validation. Recycle all application pools after making this change.
  • Defense in depth: Regardless of patch status, organizations should verify that Telerik.Upload.ConfigurationHashKey is explicitly set to a strong, randomly generated value in web.config on all Telerik AJAX deployments.

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