In Progress® Telerik® Report Server prior to version 12.3.26.1110, an external control of a system configuration setting vulnerability allows an unauthenticated remote attacker to influence the server address used by Report Server when generating links and notifications. With use...
Product
Progress Software Telerik Report Server vulnerabilities
14 published CVES affecting Progress Software Telerik Report Server, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 14
- Critical
- 2
- High
- 6
- Medium
- 6
- Low
- 0
- Unscored
- 0
- CISA KEV
- 1
Latest Progress Software Telerik Report Server CVEs
Newest publication first
-
HighCVSS 8.8 EPSS 0.50%
-
MediumCVSS 6.3 EPSS 0.27%
In Progress® Telerik® Report Server prior to version 12.3.26.1110, an incorrect authorization vulnerability in the Web Report Designer allows an authenticated attacker with low privileges to perform unauthorized operations on shared report resources, affecting their integrity and...
-
CVE-2026-106155 Stored Cross-site Scripting (XSS) in Telerik Report Server Web Report Viewers
PublishedHighCVSS 8.9 EPSS 0.20%In Progress® Telerik® Report Server prior to version 12.2.26.1007, a stored cross-site scripting vulnerability in the shared reporting engine allows an authenticated report author to embed javascript: or vbscript: URLs in report navigation actions or HTML text box links. When ano...
-
HighCVSS 7.1 EPSS 0.15%
In Progress® Telerik® Report Server prior to version 12.2.26.1007, incorrect privilege assignment in the service-agent SignalR hub allows an authenticated user, including a low-privilege or guest account with a valid bearer token, to register as a trusted service agent. On the ne...
-
MediumCVSS 6.5 EPSS 0.31%
In Progress® Telerik® Report Server, versions prior to 2025 Q1 (11.0.25.211) when using the older .NET Framework implementation, communication of non-sensitive information between the service agent process and app host process occurs over an unencrypted tunnel, which can be subje...
-
MediumCVSS 6.2 EPSS 0.11%
In Progress® Telerik® Report Server versions prior to 2024 Q4 (10.3.24.1112), the encryption of local asset data used an older algorithm which may allow a sophisticated actor to decrypt this information.
-
HighCVSS 8.8 EPSS 0.33%
In Progress® Telerik® Report Server versions prior to 2024 Q3 (10.2.24.806), a credential stuffing attack is possible through improper restriction of excessive login attempts.
-
MediumCVSS 6.5 EPSS 0.34%
In Progress® Telerik® Report Server versions prior to 2024 Q3 (10.2.24.806), an HTTP DoS attack is possible on anonymous endpoints without rate limiting.
-
HighCVSS 8.8 EPSS 0.33%
In Progress® Telerik® Report Server versions prior to 2024 Q3 (10.2.24.806), a password brute forcing attack is possible through weak password requirements.
-
CriticalCVSS 9.8 EPSS 2.0%
In Progress® Telerik® Report Server versions prior to 2024 Q2 (10.1.24.709), a remote code execution attack is possible through an insecure deserialization vulnerability.
-
CriticalCVSS 9.8 EPSS 97.5% CISA KEV added 2024-06-13 Exploited in the wild Framework module Public exploit
In Progress Telerik Report Server, version 2024 Q1 (10.0.24.305) or earlier, on IIS, an unauthenticated attacker can gain access to Telerik Report Server restricted functionality via an authentication bypass vulnerability.
-
MediumCVSS 5.3 EPSS 0.43%
In Progress Telerik Report Server, version 2024 Q1 (10.0.24.305) or earlier, on IIS, an unauthenticated attacker can gain access to Telerik Report Server restricted functionality via a trust boundary violation vulnerability.
-
MediumCVSS 6.5 EPSS 0.70%
An information disclosure vulnerability exists in Progress Telerik Report Server, version 2024 Q1 (10.0.24.305) or earlier, allows low-privilege attacker to read systems file via XML External Entity Processing.
-
HighCVSS 8.8 EPSS 34.2% Framework module
In Progress® Telerik® Report Server versions prior to 2024 Q1 (10.0.24.130), a remote code execution attack is possible through an insecure deserialization vulnerability.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.