Security readout for executives and security teams
Plain-English summary
NVIDIA OpenShell versions through 0.0.33 may inadequately reject dangerous inputs when creating sandboxes. A low-privileged network user could potentially cross security boundaries, execute code, gain privileges, access or alter data, or disrupt service. The potential impact is severe, but the supplied sources do not establish active exploitation.
Executive priority
Treat this as an immediate remediation priority for affected, reachable deployments. The combination of network access, low required privileges, no user interaction, and potentially complete system impact creates substantial business risk. Prioritize internet-facing, shared, or untrusted-user environments first, while recognizing that active exploitation is not established by the supplied evidence.
Technical view
The sandbox provisioning API can construct an incomplete list of disallowed inputs, classified as CWE-184. CVSS 3.1 rates it 9.9: network-accessible, low complexity, low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact. OpenShell versions 0 through 0.0.33 are listed as affected.
Likely exposure
Exposure is most likely where OpenShell 0 through 0.0.33 permits low-privileged users to reach the sandbox provisioning API over a network. Actual risk depends on deployed versions, API accessibility, authentication controls, and whether potentially untrusted users can provision sandboxes.
Exploitation context
The CVSS vector indicates remote, low-complexity exploitation requiring low privileges and no user interaction. Successful exploitation might affect systems beyond the vulnerable component. This CVE is not listed as KEV in the supplied bundle, and the cited information provides no evidence of active exploitation or a public exploit.
Researcher notes
CWE-184 describes an incomplete denylist, which can leave dangerous inputs unblocked. The supplied description does not identify specific parameters, bypass conditions, indicators of compromise, or a named fixed version. Validation should therefore focus on version exposure, provisioning access boundaries, vendor guidance, and defensive log review without assuming undocumented exploit mechanics.
Mitigation direction
- Consult NVIDIA advisory 5872 and apply the vendor-supported corrected release when identified.
- Until remediated, restrict the provisioning API to trusted users and management networks.
- Suspend sandbox provisioning by untrusted or minimally privileged accounts where operationally feasible.
- Monitor NVIDIA guidance for confirmed remediation details and any additional affected configurations.
Validation and detection
- Inventory all OpenShell deployments and identify versions through 0.0.33.
- Confirm which users and network paths can access the sandbox provisioning API.
- Review provisioning logs for unexpected inputs, failures, privilege changes, or anomalous sandbox activity.
- After remediation, verify the installed version and retest API authorization and input controls defensively.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-184: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-65083 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16nvidiaVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://nvd.nist.gov/vuln/detail/CVE-2026-65083CVE reference, nvidia
- https://www.cve.org/CVERecord?id=CVE-2026-65083CVE reference, nvidia
- https://github.com/NVIDIA/product-security/tree/main/2026/5872CVE reference, nvidia
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incomplete List of Disallowed Inputs
Incomplete List of Disallowed Inputs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.