Progress Telerik Reporting up to 19.0.25.211 Report Designer deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.65+ |
Summary
A vulnerability identified as problematic has been detected in Progress Telerik Reporting. Affected by this issue is some unknown functionality of the component Report Designer. Performing a manipulation results in deserialization. This vulnerability is known as CVE-2026-106140. Attacking locally is a requirement. No exploit is available. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Progress Telerik Reporting. This affects some unknown functionality of the component Report Designer. The manipulation with an unknown input leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In Progress® Telerik® Reporting prior to version 20.3.26.1110, a deserialization of untrusted data vulnerability in the .NET Framework report designers allows a local attacker with low privileges to execute arbitrary code in the context of the designer process when the user performs certain editing operations.
The advisory is shared at telerik.com. This vulnerability is uniquely identified as CVE-2026-106140 since 10/06/2026. The exploitability is told to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 20.3.26.1110 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.3
CNA Vector (ProgressSoftware): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Telerik Reporting 20.3.26.1110
Timeline
10/06/2026 CVE reserved11/12/2026 Advisory disclosed
11/12/2026 VulDB entry created
11/12/2026 VulDB entry last update
Sources
Advisory: telerik.comStatus: Confirmed
CNA: ProgressSoftware
CVE: CVE-2026-106140 (🔒)
GCVE (CVE): GCVE-0-2026-106140
GCVE (VulDB): GCVE-100-436305
Entry
Created: 11/12/2026 11:01Changes: 11/12/2026 11:01 (64)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.