CVE
Progress Telerik Reporting code execution in report designers via deserialization
Affects the .NET Framework Standalone Report Designer and Visual Studio Report Designer of Telerik Reporting before 20.3.26.1110. The .NET 8+ report designer is not affected. Fixed in 20.3.26.1110.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 20.3.26.1110
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects the .NET Framework report designers (Standalone Report Designer and Visual Studio Report Designer) before version 20.3.26.1110. The .NET 8+ report designer is not affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.23% · 14th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Progress Software's Telerik Reporting report designers contain a deserialization flaw in the .NET Framework versions that lets an attacker run arbitrary code in the designer process. An attacker must already have a local account with low privileges, and the attack works only when a user performs certain editing operations.
Read the original description
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.
Who should check
Teams running Telerik Reporting .NET Framework report designers (Standalone or Visual Studio) before 20.3.26.1110; .NET 8+ designers are not affected.
Read the source excerpt
“Progress® Telerik® Reporting .NET Framework report designers (Standalone Report Designer and Visual Studio Report Designer), versions >= 0 and < 20.3.26.1110”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.3/10CVSS 7.3
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects the .NET Framework report designers (Standalone Report Designer and Visual Studio Report Designer) before version 20.3.26.1110. The .NET 8+ report designer is not affected.Upgrade to a fixed version: 20.3.26.1110.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-106140 (Deserialization of Untrusted Data in Telerik Reporting Report Designers), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-106140 (entry last updated 2026-11-12):
Affected:
- Progress Software Telerik Reporting: fixed in 20.3.26.1110
Fixed versions: 20.3.26.1110.
Conditions (all must be true for the bug to be hit):
- Affects the .NET Framework report designers (Standalone Report Designer and Visual Studio Report Designer) before version 20.3.26.1110. (source: https://www.telerik.com/products/reporting/documentation/knowledge-base/kb-security-deserialization-of-untrusted-data-cve-2026-106140)
- The .NET 8+ report designer is not affected. (source: https://www.telerik.com/products/reporting/documentation/knowledge-base/kb-security-deserialization-of-untrusted-data-cve-2026-106140)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, a user action.
CISA KEV: CVE-2026-106140 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-106140 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.telerik.com/products/reporting/documentation/knowledge-base/kb-security-deserialization-of-untrusted-data-cve-2026-106140
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-106140
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-106140"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Progress Software Telerik Reporting
fixed in 20.3.26.1110
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-106140
Is CVE-2026-106140 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The report designer deserializes untrusted data, which lets an attacker execute arbitrary code in the context of the designer process.Source: telerik.com
Which versions are affected by CVE-2026-106140?
Telerik Reporting: before 20.3.26.1110.Source: cve.now feed data
Am I affected, and how do I check?
The .NET Framework report designers (Standalone Report Designer and Visual Studio Report Designer) in Telerik Reporting versions before 20.3.26.1110 are affected. The .NET 8+ report designer is not affected. To check, identify the Telerik Reporting version and the designer type in use.Source: telerik.com
How do I fix CVE-2026-106140?
Update the .NET Framework report designers to version 20.3.26.1110 or later.Source: telerik.com