/

CVE-2026-26002

Severity:

CRITICAL RISK

(9.8)

Injection Vulnerability in Open OnDemand Files Application

CVE-2026-26002

Analyzed

Vulnerability type

Category:

Injection Vulnerability

CWE:

CWE-74

Impact:

Potential Remote Code Execution and System Compromise

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

The Files application in Open OnDemand versions prior to 4.0.9 and 4.1.3 is susceptible to injection through malicious input when users navigate to directories.

If an attacker can influence the directory path or related navigation parameters, this flaw can enable execution of unintended commands or queries in the underlying system, leading to severe compromise of the HPC environment.

Affected context

The vulnerability exists in the Files application component of Open OnDemand when handling directory navigation input.

It is relevant in deployments where:

  • End users can browse or manipulate file paths through the web portal
  • Directory paths or navigation parameters are derived from user-controlled input
  • Input is passed into downstream interpreters (e.g., shells, system utilities, or command wrappers) without strict sanitization or encoding

The risk is elevated in shared HPC environments where the portal has access to sensitive data or elevated system commands.

Exploit preconditions

  • Attack surface: Web interface of the Open OnDemand Files application
  • Required access: Ability to authenticate or otherwise reach the Files application and supply directory navigation input
  • Trigger point: Submitting or following crafted directory paths or navigation parameters that are processed by the Files app
  • Why exploitation is possible: User-controlled directory values are not consistently normalized, validated, or safely encoded before being passed to backend interpreters, enabling injection as defined by CWE-74

Why this happens

This issue stems from improper handling of externally supplied directory navigation input within the Files application.

Instead of treating user-supplied paths as opaque data, the application allows them to flow into downstream components (such as shell commands, scripts, or APIs that interpret special characters or meta-syntax) without robust, centralized validation and encoding.

This aligns with CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component, where untrusted data is embedded into a string that is later processed by another interpreter in a way that can alter its intended behavior.

Potential impact

  • Remote execution of unintended commands in the HPC environment
  • Unauthorized access to or modification of user and project data
  • Escalation of privileges within the portal context or connected systems
  • Lateral movement across user accounts or compute nodes via compromised portal actions
  • Disruption of HPC workloads, including job tampering or data corruption

General mitigation guidance

Effective mitigation focuses on treating all directory navigation input as untrusted and ensuring it cannot alter downstream interpreter behavior.

Recommended patterns include:

  • Enforcing strict allowlists for valid path patterns and restricting navigation to known root directories or chroot-like scopes
  • Normalizing and canonicalizing paths (e.g., resolving .., symbolic links) before further processing, and rejecting any that escape allowed directories
  • Avoiding direct concatenation of user input into shell commands or interpreter calls; instead, use parameterized APIs or structured arguments
  • Centralizing validation logic so all Files application entry points use the same robust checks
  • Applying least-privilege execution for any helper processes invoked by the Files application to limit blast radius if injection occurs

How teams detect issues like this

Organizations can detect this class of vulnerability by:

  • Performing static analysis to identify code paths where user-controlled path variables are concatenated into command strings or passed to interpreters without sanitization
  • Using security-focused code review checklists that flag any use of shell calls, system utilities, or interpreter bindings receiving directory input
  • Implementing centralized logging for suspicious navigation patterns (e.g., directory names containing metacharacters, control operators, or traversal sequences) and monitoring for anomalies
  • Incorporating dynamic application security testing (DAST) that fuzzes directory navigation inputs with special characters and observes backend behavior

Sources

SourceLink
github.comgithub.com/OSC/ondemand/commit/23cb167222886fdd8415277ca5c1215f4c32629c
github.comgithub.com/OSC/ondemand/commit/37f0ae4efb222e9c0af250feae860a720427df16
github.comgithub.com/OSC/ondemand/security/advisories/GHSA-f83q-mhrr-3cr2

Frequently asked

questions

Yes, it can be remotely exploitable through the Open OnDemand web interface, provided an attacker can reach the Files application and supply crafted directory navigation input.

The attacker typically needs access to the Files application, which in many deployments requires user authentication to the HPC portal. The exact access level needed depends on how the portal is exposed and configured.

The safest pattern is to strictly validate and normalize all directory navigation input, restrict navigation to approved base directories, and ensure that any interaction with downstream components uses parameterized calls rather than string concatenation.

Prevention involves adopting a secure-by-default input handling strategy: treat all user input as untrusted, enforce consistent validation and canonicalization for paths, avoid passing raw input into interpreters, and incorporate security checks (static analysis, code review rules, and automated tests) into the development and deployment pipeline.

Find out what's already
exploitable in your codebase.