Telerik UI for Blazor path traversal flaw rated 7.5
Telerik Blazor path traversal flaw ·
In this episode
The facts
- CVE-2026-118976 is a flaw in Progress Software Telerik UI for Blazor.
- CVE-2026-118976 is classed as relative path traversal (CWE-23).
- According to its CVSS rating, CVE-2026-118976 can be exploited remotely over the network, without any credentials and without user interaction.
- CVE-2026-118976 is rated 7.5 out of 10 on the CVSS severity scale.
Sources
The panel
Jordan Pike AI host
CVE-2026-118976 is a flaw in Progress Software Telerik UI for Blazor, and it's classed as relative path traversal, CWE-23, according to the CVE Program.
Jordan Pike AI host
It's rated 7.5 out of 10 on the CVSS severity scale. According to that rating, it can be exploited remotely over the network, without any credentials and without user interaction.
Jordan Pike AI host
If your developers build on Telerik UI for Blazor, this one is yours. If you don't know whether they do, that's your first job. Maya, start us off: what kind of bug is this?
Maya Okafor AI analyst
Path traversal happens when an application builds a file location from outside input and never confirms the result still lands inside the folder it meant to serve from. It keeps happening because path handling looks harmless until someone feeds it something unexpected. The facts don't say which part of the component is affected, so I won't guess. A complete fix resolves the final path and checks it against an allowed base directory. Stripping out bad-looking sequences is only a partial fix, and those filters tend to come back as new bugs. Once a patch ships, check that, and look at nearby code that also takes file names.
Maya Okafor AI analyst
Path traversal is a bug class old enough to rent a car, and it still turns up in new components. Vintage.
Jordan Pike AI host
Aged well, then. Dex, how does an attacker see it?
Dex Moreno AI analyst
The rating is the scary part: network reachable, no credentials, no clicking. If an app using this component is exposed, the attacker only needs to reach it. What that gets them depends on what the app can touch. The facts don't say whether files are read or written. Generally, though, a traversal bug is attractive because applications keep configuration, keys and connection details on disk. Those can lead to databases and other services behind the app. Bugs with this profile tend to get weaponised quickly once they're public, so the part you can still control is exposure.
Dex Moreno AI analyst
So my priority is exposure over score. A 7.5 on an internet-facing app takes priority over a higher rating on a non-exposed component. Find the exposed apps first, then patch, and assume someone may already have looked.
Maya Okafor AI analyst
Network, no credentials and no interaction is exactly the profile where waiting for the normal patch cycle is a bet. Nothing in the facts says whether a fix exists yet. So the action is to inventory every app that uses this component now. Apply the fix as soon as one ships. If you need a stopgap, treat it as a bridge and give it an end date.
Jordan Pike AI host
So Dex says rank by exposure and Maya says inventory everything now and patch on arrival. Those fit together if you do it in that order. Sam, what's left for the response side?
Sam Kowalski AI analyst
Before anyone says 'no evidence of compromise', find out how long your web and application logs go back. If the answer is not long, that sentence means nothing. Pull the logs for the apps that use this component and look for requests for files they shouldn't be serving. Also assume anything exposed could have been probed before the CVE was public. My action: confirm your log retention today, before you need it.
Sam Kowalski AI analyst
Your logs say nothing happened, I'm sure. They also say nothing about last month, because they were deleted. Very reassuring.
Jordan Pike AI host
Silence is golden. Rina, who's behind it?
Rina Takahashi AI analyst
Nobody, as far as the facts go. Nothing here attributes this flaw to an actor or a campaign, and none of the facts say it's being exploited. So treat any forum post or social media claim about it as a claim, and ask who says so and how confident they are. My action: watch for confirmation from the CVE Program or the vendor, and don't let rumour set your priorities.
Jordan Pike AI host
Monday, then: find where Telerik UI for Blazor runs, start with whatever is exposed, check your log retention, and apply the fix as soon as there's one. We'll update you when there's more.