CVE-2026-59179
Description
A flaw was found in @openhop/server. The application fails to properly validate flow identifiers received in route parameters before constructing file system paths. An unauthenticated attacker can exploit this flaw by sending crafted requests containing relative path sequences to access locations outside the intended storage directory, either directly over the network or indirectly through a malicious webpage abusing permissive Cross-Origin Resource Sharing (CORS) settings. Successful exploitation allows an attacker to permanently delete critical files or expose sensitive configuration files accessible to the application, resulting in data loss, service disruption, and information disclosure.
Statement
Red Hat Product Security has rated this vulnerability as Important because an unauthenticated remote attacker can traverse directory paths to delete or view YAML files, posing significant threats to service availability and data integrity without requiring privileges. The elevated risk is driven by unauthenticated access combined with permissive cross-origin policies, which allow exploitation across the network or through third-party browser contexts. However, the @openhop/server component is not distributed or supported in Red Hat products, resulting in no direct impact on Red Hat environments.
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.
