CVE-2024-6097
CVE-2024-6097 is a medium-severity vulnerability in Progress Telerik Reporting with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.
Key facts
- Severity: Medium (CVSS 3.x base score 5.3)
- EPSS exploit prediction: 1% (46th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-4302
- Weakness: CWE-22
- Affected product: Progress Telerik Reporting
- Published:
- Last modified:
Description
In Progress® Telerik® Reporting versions prior to 2025 Q1 (19.0.25.211), information disclosure is possible by a local threat actor through an absolute path vulnerability.
Frequently asked questions
- What is CVE-2024-6097?
- In Progress® Telerik® Reporting versions prior to 2025 Q1 (19.0.25.211), information disclosure is possible by a local threat actor through an absolute path vulnerability.
- How severe is CVE-2024-6097?
- CVE-2024-6097 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
- Is CVE-2024-6097 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (46th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2024-6097?
- CVE-2024-6097 affects Progress Telerik Reporting. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2024-6097?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2024-6097 have an EU (EUVD) identifier?
- Yes. CVE-2024-6097 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-4302.
- When was CVE-2024-6097 published?
- CVE-2024-6097 was published on 2025-02-12 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:progress:telerik_reporting:*:*:*:*:*:*:*:*
More vulnerabilities in Progress Telerik Reporting
- CVE-2024-8014 — High (CVSS 8.8): In Progress Telerik Reporting versions prior to 2024 Q3 (18.2.24.924), a code execution attack is possible through…
- CVE-2024-6096 — High (CVSS 8.8): In Progress® Telerik® Reporting versions prior to 18.1.24.709, a code execution attack is possible through object…
- CVE-2024-1856 — High (CVSS 8.5): In Progress® Telerik® Reporting versions prior to 2024 Q1 (18.0.24.130), a code execution attack is possible by a…
- CVE-2024-8048 — High (CVSS 7.8): In Progress Telerik Reporting versions prior to 2024 Q3 (18.2.24.924), a code execution attack is possible using object…
- CVE-2024-7840 — High (CVSS 7.8): In Progress Telerik Reporting versions prior to 2024 Q3 (18.2.24.924), a command injection attack is possible through…
- CVE-2024-0832 — High (CVSS 7.8): In Telerik Reporting versions prior to 2024 R1, a privilege elevation vulnerability has been identified in the…
All CVEs affecting Progress Telerik Reporting →
Other CWE-22 (Path Traversal) vulnerabilities
- CVE-2026-77312 — Critical (CVSS 10.0): Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, the earlier CVE-2026-67429…
- CVE-2026-121351 — Critical (CVSS 10.0): Adobe Connect is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')…
- CVE-2026-121489 — Critical (CVSS 10.0): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Juneau. The…
- CVE-2026-122013 — Critical (CVSS 10.0): A vulnerability was detected in Comfast CF-WR632AX 2.6.0.1. Affected by this vulnerability is an unknown functionality…
- CVE-2026-61738 — Critical (CVSS 10.0): SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to…
- CVE-2026-112690 — Critical (CVSS 10.0): This issue was addressed with improved input validation. This issue is fixed in iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2…