Description
In Progress® Telerik® UI for AJAX prior to v2026.2.708, when Telerik.Upload.ConfigurationHashKey is absent and machineKey is not explicitly configured, upload metadata integrity protection may fall back to a predictable default key, enabling attackers to forge protected upload metadata and unlock further exploit chains.
Published: 2026-07-22
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability exists in Progress Software Telerik UI for ASP.NET AJAX versions prior to 2026.2.708. The upload component signs metadata with a configuration hash key; when the Telerik.Upload.ConfigurationHashKey setting is omitted and the application does not define a machineKey, it falls back to a predictable default key. This cryptographic weakness (CWE‑321) allows an attacker to forge signed metadata, bypassing the integrity check that protects upload data. The impact is that forged metadata can be accepted by the application, potentially leading to broader exploitation within the system.

Affected Systems

Installs of Progress Software Telerik UI for ASP.NET AJAX that rely on the default configuration hash key are affected. Any instance using the upload component without setting Telerik.Upload.ConfigurationHashKey in web.config and without an explicit machineKey stanza is vulnerable. Versions older than 2026.2.708 are susceptible.

Risk and Exploitability

The CVSS score of 7.5 indicates a high severity, and the EPSS score of <1% suggests a low exploitation probability at the time of analysis. The vulnerability is not listed in CISA’s KEV catalog. The description does not specify whether authentication is required for the exploitation path, so the exact attack vector is not determined from the data. Nevertheless, because the fallback to a predictable key trivializes the forging of metadata, an attacker who can reach the upload endpoint could potentially exploit the flaw if additional conditions permit.

Generated by OpenCVE AI on August 3, 2026 at 23:42 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Telerik UI for ASP.NET AJAX component to version 2026.2.708 or later, where the default key fallback has been removed.
  • If an upgrade is not immediately possible, configure a strong, random value for Telerik.Upload.ConfigurationHashKey in web.config.
  • Define a proper machineKey stanza in web.config to ensure that the application does not rely on any default keys.

Generated by OpenCVE AI on August 3, 2026 at 23:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 28 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
First Time appeared Progress
Progress telerik Ui For Asp.net Ajax
Vendors & Products Progress
Progress telerik Ui For Asp.net Ajax

Wed, 22 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 22 Jul 2026 14:00:00 +0000

Type Values Removed Values Added
Description In Progress® Telerik® UI for AJAX prior to v2026.2.708, when Telerik.Upload.ConfigurationHashKey is absent and machineKey is not explicitly configured, upload metadata integrity protection may fall back to a predictable default key, enabling attackers to forge protected upload metadata and unlock further exploit chains.
Title RadAsyncUpload Default HMAC Key Fallback Vulnerability in Telerik UI for ASP.NET AJAX
Weaknesses CWE-321
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}


Subscriptions

Progress Telerik Ui For Asp.net Ajax
cve-icon MITRE

Status: PUBLISHED

Assigner: ProgressSoftware

Published:

Updated: 2026-07-22T19:14:27.027Z

Reserved: 2026-06-24T13:46:38.790Z

Link: CVE-2026-13184

cve-icon Vulnrichment

Updated: 2026-07-22T19:14:23.394Z

cve-icon NVD

Status : Analyzed

Published: 2026-07-22T14:17:13.927

Modified: 2026-08-06T18:09:11.080

Link: CVE-2026-13184

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-03T23:45:06Z

Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key