CVE-2026-118975 · Package
NO FIX YET · SEE WHAT TO DO
Telerik Reporting resolves external XML entities inside SVG content supplied to a report, so an attacker can read local or UNC files and make server-side network requests from the rendering host. The attacker needs a low-privilege account that can supply SVG content to a report.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that run Telerik Reporting on a server and let users supply SVG content to reports are exposed. The risk comes from the rendering host reading files or making network requests, so reports built only from trusted content with no user-supplied SVG are lower risk.
Not affected if no-user-supplied-svg, telerik-reporting-below-affected-range
Who cares dotnet, self-hosted, telerik-reporting
20.3.26.1110 or later to be outside the affected range.20.3.26.1110 or later.In Progress® Telerik® Reporting prior to version 20.3.26.1110, improper restriction of XML external entity references in the SVG processing engine allows an authenticated attacker with low privileges who can supply SVG content to a report to read local or UNC files, or trigger server-side network requests, from the report rendering host. External XML entities in SVG content were resolved without applying the configured strict resource resolver and report path validation. Disclosed content is limited by the permissions of the rendering process and by what the rendered report output exposes.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.