Telerik UI for ASP.NET AJAX: Use of Hard-coded Cryptographic Key
CVE-2026-13184 is a high-severity use of hard-coded cryptographic key vulnerability in Telerik UI for ASP.NET AJAX from Progress Software, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2026.2.708 as the first without the flaw, so updating Telerik UI for ASP.NET AJAX to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.31% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Telerik UI for ASP.NET AJAX to 2026.2.708 or a later version.
- Read the advisory on telerik.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Progress Software | Telerik UI for ASP.NET AJAX | 2010.1.309 up to, but not including, 2026.2.708 | 2026.2.708 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by CNA (progress.com).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Hard-coded Cryptographic Key
The product uses a hard-coded, unchangeable cryptographic key.
How developers prevent this class of flaw
- Prevention schemes mirror that of hard-coded password storage.
More Use of Hard-coded Cryptographic Key vulnerabilities (CWE-321)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Telerik UI for ASP.NET AJAX
- 8.1 High severity
- 7.5 High severity
- 8.1 High severity
- 7.5 High severity
- 8.1 High severity
- 8.1 High severity
Recent Use of Hard-coded Cryptographic Key vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 8.3 High severity
- 7.5 High severity
- 8.1 High severity
- 7.1 High severity
Spotted an error? Tell us.