CVE-2026-118976 in Telerik UI for Blazorinfo

Summary

by MITRE • 11/13/2026

In Progress® Telerik® UI for Blazor versions v11.1.0 through v14.0.0, the demo application's Chat AI Integration example contains a relative path traversal vulnerability that could allow an attacker to read files outside of the chat attachments folder that are within the server's filesystem scope.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/13/2026

The identified security flaw resides in the Progress Telerik UI for Blazor framework, specifically affecting versions ranging from v11.1.0 through v14.0.0. This vulnerability is located within a demo application feature known as Chat AI Integration, which serves as an example of how developers can integrate artificial intelligence capabilities into their web applications using this library. While the presence of such vulnerabilities in demonstration code may seem less critical than those in core production libraries, it poses significant risks when these examples are copied directly into real-world projects without adequate security review or hardening measures. The specific nature of the flaw is a relative path traversal vulnerability, which allows an attacker to manipulate file system paths to access resources that should remain inaccessible.

From a technical perspective, this issue stems from insufficient validation and sanitization of user-supplied input when processing requests related to chat attachments. In typical implementations, applications restrict file operations to specific directories to prevent unauthorized data exposure. However, in this instance, the application fails to properly normalize or validate the path provided by the client before using it to locate files on the server's filesystem. By utilizing relative path sequences such as dot-dot-slash (..), an attacker can navigate up the directory tree from the intended chat attachments folder. This manipulation enables the reading of arbitrary files that reside within the broader scope of the server's accessible file system, effectively bypassing the intended isolation boundaries established by the application logic.

The operational impact of this vulnerability is primarily centered on information disclosure and potential data exfiltration. An attacker who can exploit this flaw could read sensitive configuration files, source code containing hardcoded credentials or API keys, database connection strings, or other proprietary business logic stored in adjacent directories. This level of access does not directly allow for remote code execution but serves as a powerful reconnaissance tool that can facilitate further attacks. For instance, obtaining environment variables or secret management configurations from this vulnerability could lead to full system compromise if those secrets are used elsewhere with elevated privileges. The risk is amplified because the flaw exists in a feature designed for interactive chat functionality, which may be exposed to end-users depending on how the demo application is deployed and configured.

This vulnerability aligns closely with Common Weakness Enumeration (CWE) category CWE-22: Improper Limitation of a Pathname to a Restricted Directory, also known as path traversal or directory traversal. The failure to restrict file access to a specific sandboxed area represents a classic implementation error where the application trusts user input regarding file locations without rigorous validation. In terms of offensive security frameworks, this exploitation technique corresponds to ATT&CK tactic TA0006: Credential Access and sub-technique T1530: Data from Local System, as it involves reading files from the local filesystem to gather intelligence or steal credentials stored in plaintext configuration files.

To mitigate this risk, developers must ensure that any code derived from demo applications is thoroughly audited before deployment. The immediate remediation involves implementing strict input validation for all file path parameters. This includes rejecting inputs containing relative path sequences and ensuring that resolved paths are strictly confined within the designated attachment directory using canonicalization techniques. Additionally, employing a whitelist approach where only specific allowed characters or extensions are permitted can further reduce the attack surface. For organizations still running affected versions of Telerik UI for Blazor, upgrading to a patched version is essential if this feature is utilized in production environments. Furthermore, applying principle of least privilege by restricting the application's filesystem permissions ensures that even if traversal occurs, the attacker cannot access critical system files or sensitive data located outside the designated web root or application directories.

Responsible

ProgressSoftware

Reservation

10/29/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00373

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!