Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeploy rogue gateway server
-
DeliveryRedirect victim OpenShell client to rogue endpoint
-
ExploitInject OS commands in malicious gateway response
-
ExecutionClient executes injected commands on host OS
-
ImpactExfiltrate data or persist on victim system
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that a victim user actively connect to or interact with an attacker-controlled or attacker-compromised gateway - this is the UI:R condition in the CVSS vector. The attacker must control a network endpoint that the OpenShell client treats as a gateway (e.g., through DNS hijacking, BGP manipulation, SSRF, a compromised gateway host, or by convincing the user to point their client at a malicious URL). No authentication on the attacker's side is required (PR:N). No special privileges are required on the victim system beyond having OpenShell installed and a user willing to initiate the gateway connection. Limiting factors: the required user interaction (UI:R) means fully automated mass exploitation without any user participation is not possible; exploitation is also constrained to platforms and versions where OpenShell is installed. Non-default or misconfigured gateway settings that direct clients to external, untrusted endpoints would substantially increase real-world risk. |
| Impact | The CVSS 8.8 score reflects a genuinely high-severity finding: network-accessible (AV:N), low complexity (AC:L), no attacker privileges required (PR:N), and high impact across all three pillars (C:H/I:H/A:H). The single limiting factor is UI:R - the victim must interact with the malicious gateway, which reduces the attack surface compared to a fully autonomous exploit. No EPSS score was provided in the input data, so exploitation probability cannot be quantified. The vulnerability is not listed in the CISA KEV catalog and no proof-of-concept code has been identified, indicating that as of this analysis, exploitation appears theoretical rather than observed. The realistic risk depends heavily on deployment architecture: organizations connecting OpenShell clients to externally-reachable or shared gateway infrastructure face substantially higher exposure than those in isolated, trusted network environments. The attacker-in-the-middle or rogue-gateway scenario is the primary threat model, which requires either network positioning or social engineering to succeed. |
| Exploit ScenarioDerived | An attacker deploys a rogue gateway server mimicking a legitimate NVIDIA OpenShell endpoint, then lures a target user into connecting to it - for example, through DNS poisoning, a misconfigured gateway URL, or social engineering. The malicious gateway returns a crafted response containing shell metacharacters that OpenShell passes unsanitized to the OS command interpreter, achieving arbitrary code execution under the victim user's operating system context. No public proof-of-concept has been identified, but the CWE-78 injection class is well-understood and the attack complexity is rated low by the vendor. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
OS command injection in NVIDIA OpenShell across all supported platforms allows a network-accessible malicious gateway to execute arbitrary operating system commands on a victim host when a user interacts with that gateway. The CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R) reflects that an attacker requires no privileges on the victim system but does require the victim to interact with a malicious or attacker-controlled gateway endpoint. Successful exploitation yields full code execution, data tampering, and information disclosure - with no public exploit or CISA KEV listing identified at time of analysis.
RemediationAI
Consult the NVIDIA product security advisory at https://github.com/NVIDIA/product-security/tree/main/2026/5872 for the vendor-released patch; no specific fixed version number was present in the available input data, so upgrade to the version identified in that advisory as the primary remediation. As a compensating control pending patching, restrict OpenShell clients to connect exclusively to known-trusted, authenticated gateway endpoints - for example, by enforcing gateway certificate pinning or network ACLs that block connections to any gateway not on an approved allowlist, which directly addresses the malicious-gateway threat model. Additionally, deploying the OpenShell client behind a network boundary that prevents connection to arbitrary external gateways (e.g., egress filtering on relevant ports) limits the attacker's ability to position a rogue gateway. Note that network-level controls will not protect against a compromised legitimate gateway, so patching remains essential. No workarounds eliminate the root CWE-78 injection flaw without the vendor fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
NVIDIA OpenShell (CPE: cpe:2.3:a:nvidia:openshell:*:*:*:*:*:*:*:*) is a shell or management interface product from NVIDIA spanning all platforms, suggesting a cross-platform client that communicates with a backend gateway service. CWE-78 (Improper Neutralization of Special Elements used in an OS Command - OS Command Injection) is the root cause: the client application passes data received from the gateway to an OS shell interpreter without adequate sanitization or escaping, allowing a malicious gateway to embed shell metacharacters or commands in responses that the client then executes in the underlying operating system context. This class of vulnerability is distinct from a buffer overflow or memory corruption issue - it is an input-handling failure in the command construction logic, typically exploitable wherever the application calls system(), popen(), exec(), or equivalent constructs with untrusted network-supplied input.
Know when Openshell gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Network vector and no attacker privileges required; UI:R reflects mandatory victim interaction with the malicious gateway; full C/I/A impact consistent with arbitrary OS command execution.
Primary rating from Vendor (nvidia).
CVSS VectorVendor: nvidia
DescriptionCVE.org
NVIDIA OpenShell for all platforms contains a vulnerability where a malicious gateway could cause OS command injection. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.
Articles & Coverage 1
Executive ViewAI
NVIDIA OpenShell contains a network-accessible command injection vulnerability (CVSS 8.8) affecting all supported platforms that allows attackers to execute arbitrary system commands when users interact with malicious or compromised gateway endpoints. All organizational endpoints running OpenShell are at risk of complete compromise including data access, system tampering, and potential lateral movement. Leadership should prioritize mitigation planning immediately, as no vendor patch is currently available.
Restrict OpenShell gateway connectivity to pre-approved endpoints via firewall rules; deploy endpoint detection and response (EDR) to monitor for suspicious child processes from OpenShell; require multi-factor authentication on systems running OpenShell; disable OpenShell where operationally feasible; segment affected systems from sensitive data and critical infrastructure; maintain network-based detection signatures for exploitation attempts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Privilege escalation and remote code execution in NVIDIA OpenShell for Linux stem from an incomplete deny-list in its sa
Sandbox escape in NVIDIA OpenShell for Linux lets a low-privileged actor already operating inside the sandbox break its
Path traversal in NVIDIA OpenShell Sandbox for Linux permits low-privileged network-authenticated attackers to bypass L7
OS command injection in NVIDIA OpenShell for Linux's sandbox exec handler allows a low-privileged, network-accessible at
Improper output encoding in NVIDIA OpenShell's inference proxy on Linux allows a local low-privileged attacker to cause
EUVD-2026-66090
GHSA-r343-96vw-2jfv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB