CVE-2024-1801: In Progress® Telerik® Reporting versions prior to 2024 Q1 (18.0.24.130), a code execution attack is possible

Q: How do I fix CVE-2024-1801?

telerik reporting: upgrade to 18.0.24.130. Exact commands for each OS are on this page.

Q: Is CVE-2024-1801 being exploited?

CVE-2024-1801 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-1801 affect?

CVE-2024-1801 affects telerik reporting. Severity is high (CVSS 7.7). In Progress® Telerik® Reporting versions prior to 2024 Q1 (18.0.24.130), a code execution attack is possible by a local threat actor through an insecure deserialization vulnerability.

Routine

HIGH 7.7UPGRADE

CVE-2024-1801 is a high-severity flaw (CVSS 7.7) affecting telerik reporting. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In Progress® Telerik® Reporting versions prior to 2024 Q1 (18.0.24.130), a code execution attack is possible by a local threat actor through an insecure deserialization vulnerability.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.7 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-502
Published	2024-03-20
Last modified	2026-06-17

Publisher (CNA): Progress Software Corporation · Vendor: progress

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-03-20 13:15 UTCPublished CVE record published
2026-06-17 07:05 UTCUpdated Record last modified

progress telerik reporting UPGRADE

Affected: < 18.0.24.130

Fixed in: 18.0.24.130

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy telerik-reporting || rpm -q telerik-reporting || telerik-reporting --version

2. UPGRADE to 18.0.24.130 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade telerik-reporting

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade telerik-reporting

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-1801?

telerik reporting: upgrade to 18.0.24.130. Exact commands for each OS are on this page.

Is CVE-2024-1801 being exploited?

CVE-2024-1801 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-1801 affect?

CVE-2024-1801 affects telerik reporting. Severity is high (CVSS 7.7). In Progress® Telerik® Reporting versions prior to 2024 Q1 (18.0.24.130), a code execution attack is possible by a local threat actor through an insecure deserialization vulnerability.

How urgent is CVE-2024-1801?

Priority 36/100. High severity

Related CVEs

CVE-2024-8048 HIGH 7.8 UPGRADE In Progress Telerik Reporting versions prior to 2024 Q3 (18.2.24.924), a code execution attack is possible usi
CVE-2024-8014 HIGH 8.8 UPGRADE In Progress Telerik Reporting versions prior to 2024 Q3 (18.2.24.924), a code execution attack is possible thr
CVE-2024-7840 HIGH 7.8 UPGRADE In Progress Telerik Reporting versions prior to 2024 Q3 (18.2.24.924), a command injection attack is possible
CVE-2024-7294 HIGH 7.5 UPGRADE In Progress® Telerik® Report Server versions prior to 2024 Q3 (10.2.24.806), an HTTP DoS attack is possible on
CVE-2024-7293 HIGH 7.5 UPGRADE In Progress® Telerik® Report Server versions prior to 2024 Q3 (10.2.24.806), a password brute forcing attack i

References

← Back to latest CVEs