CVE-2024-8014: Progress Software Telerik Reporting · Unsafe Reflection
Affects Progress Software Telerik ReportingSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 18.2.24.924 soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 18.2.24.924
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade telerik.reporting to 18.2.24.924.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
NuGettelerik.reportingpkg:nuget/telerik.reportingOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-8014, organizations should prioritize upgrading Telerik Reporting to version 18.2.24.924 or later once available. If you cannot patch yet, restrict network access to reporting services by implementing strict firewall rules and network segmentation to limit exposure. Employ application-layer filtering or web application firewalls (WAFs) to detect and block suspicious input patterns that could trigger unsafe reflection. Conduct thorough input validation and sanitization on all user-supplied data used in dynamic code or class loading contexts. Monitor logs and network traffic for unusual activity indicative of exploitation attempts, such as unexpected class instantiations or anomalous object injection patterns. Additionally, review and harden permissions for accounts running Telerik Reporting services to minimize privilege levels. Engage with Progress Software for any interim security advisories or hotfixes. Finally, incorporate this vulnerability into incident response and threat hunting exercises to improve detection and response capabilities.
Description
In Progress Telerik Reporting versions prior to 2024 Q3 (18.2.24.924), a code execution attack is possible through object injection via an insecure type resolution vulnerability.