CVE-2024-1856: Progress Software Telerik Reporting · Deserialization of Untrusted Data
Affects Progress Software Telerik ReportingSource CVE Database V5
Not known to be exploited · CVSS 8.5 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 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
AI-suggested
Organizations should immediately upgrade Telerik Reporting to version 2024 Q1 (18.0.24.130) or later, where the vulnerability is patched. In the absence of an available patch, apply strict input validation and sanitization on all data inputs that may be deserialized by the application. Network segmentation should be employed to limit exposure of the reporting service to untrusted networks. Implement application-layer firewalls and intrusion detection/prevention systems to monitor and block suspicious deserialization payloads. Conduct thorough code reviews and security testing focusing on deserialization processes. Additionally, restrict privileges of the service account running Telerik Reporting to minimize potential damage from exploitation. Regularly monitor security advisories from Progress Software and subscribe to vulnerability feeds to stay informed about any emerging exploits or patches.
Description
In Progress® Telerik® Reporting versions prior to 2024 Q1 (18.0.24.130), a code execution attack is possible by a remote threat actor through an insecure deserialization vulnerability.