Database/AI/ML frameworks & serving
NVIDIA OpenShell: nonstandard HTTP methods bypass L7 policy on CONNECT tunnels
Impact
NVIDIA reports that OpenShell's L7 policy enforcement on HTTP CONNECT tunnels can be bypassed with nonstandard HTTP methods. A sandboxed workload can send requests that the policy was meant to block. NVIDIA rates confidentiality and integrity impact low but marks the scope as changed.
Who can reach it
Low-privileged attacker who can send traffic through an OpenShell CONNECT tunnel, normally a sandboxed workload. NVIDIA's vector is network (AV:N), while the description says local. No user interaction needed.
What to do
Update NVIDIA OpenShell to the fixed release in NVIDIA product-security bulletin 5929. The record does not give a fixed version. Until then, enforce access on the upstream services too, rather than relying on the proxy alone.
References
Related entries
- NVIDIA OpenShell: gateway accepts any sandbox host key, enabling machine-in-the-middleCVE-2026-100978 · NVIDIA OpenShell for Linux (gateway-to-sandbox transport)Medium
- NVIDIA OpenShell: HTTP request smuggling past the L7 REST proxy's policy checksCVE-2026-100981 · NVIDIA OpenShell for Linux (L7 REST proxy)Medium
- Jupyter Server: login `next` parameter allows redirect to an arbitrary external hostCVE-2025-61669 · Jupyter Server (LoginFormHandler redirect validation)Medium
- vLLM: video decoder limit bypass via sampler subclass shadowing exhausts unaccounted GPU memoryCVE-2026-100649 · vLLM (PyNvVideoCodec decoder allocation, sampler subclass accounting)Medium
- docling-serve: memory telemetry endpoints omit the auth dependency, exposing stats and forced GCCVE-2026-108749 · docling-serve (/v1/memory/stats and /v1/memory/counts endpoints)Medium
- vLLM: stale allowed_token_ids rows let one request constrain another tenant's outputCVE-2026-114049 · vLLM InputBatch.condense() (allowed_token_ids cross-request mask leak)Medium
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.