CVE-2026-86253
Description
A flaw was found in h3, an npm package. An unauthenticated remote attacker can exploit this vulnerability by sending crafted requests to endpoints served by the serveStatic() function. On Node.js deployments, the event.url.pathname is not properly normalized, allowing percent-encoded dot segments to be decoded into directory traversal sequences without sanitization. This path traversal vulnerability enables the attacker to read arbitrary files outside the intended static directory, leading to information disclosure.
Statement
Moderate: This path traversal vulnerability in the h3 npm package allows an unauthenticated remote attacker to read arbitrary files from the system. The flaw occurs in Node.js deployments utilizing the serveStatic() function, where improper normalization of percent-encoded dot segments leads to information disclosure. This impacts Red Hat OpenShift AI (RHOAI) components that incorporate the vulnerable h3 package.
Mitigation
To mitigate this vulnerability, restrict network access to services utilizing the `h3` `serveStatic()` function to trusted clients and networks only. Implement firewall rules to limit exposure of the affected component, `rhoai/odh-feature-server-rhel9`, to prevent unauthenticated remote attackers from sending crafted requests. This may impact legitimate access to static content served by the component.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.9 | N/A | 5.9 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.