NVIDIA Isaac Launchable CVE-2026-24212

The attacker must be on the adjacent network (CVSS AV:A) - the same Layer-2 broadcast domain, VLAN, or Wi-Fi network as the Isaac Launchable host - and must be running an instance of Isaac Launchable for Linux at a version prior to 1.2 on that host. AC:H signals that additional conditions outside the attacker's control are required, most plausibly being present while sensitive data is actively transmitted and successfully interposing on or sniffing that traffic (e.g., active MITM via ARP/NDP spoofing on a switched network, or passive capture on an unswitched/wireless segment). No authentication is required (PR:N) and no user interaction is needed (UI:N). Limiting factors: internet-based attackers cannot exploit this directly, fully switched networks with port security and dynamic ARP inspection raise the bar significantly, and hosts upgraded to Isaac Launchable 1.2 or later are not affected.

The signals point to a real but bounded risk. CVSS 7.5 with C:H/I:H/A:H and SSVC Technical Impact 'total' indicate that successful exploitation is highly damaging, but the same vector qualifies it heavily: AV:A limits attackers to the adjacent network (not internet-reachable), AC:H means non-trivial conditions such as timing, positioning, or active MITM are required, and PR:N/UI:N keep it unauthenticated and non-interactive. SSVC reports Exploitation 'none' and Automatable 'no', EPSS is 0.00% / 0th percentile, and the CVE is not in CISA KEV - all consistent with no public exploit identified at time of analysis. Net effect: prioritize patching in environments where the Isaac host shares a network with untrusted devices (lab benches, shared robotics testbeds, factory floors with BYOD), but this is not a drop-everything internet-facing emergency. One caveat: NVIDIA's description lists code execution and privilege escalation as possible outcomes, which is broader than what CWE-319 alone normally implies - the chain from sniffed cleartext to RCE is not detailed in public sources and should be confirmed with the vendor advisory if precise impact modeling matters.

An attacker connected to the same physical or wireless LAN as an Isaac Launchable host (for example, a contractor laptop on a robotics lab network or a compromised IoT device on a factory segment) positions themselves via ARP spoofing or passive monitoring and captures cleartext traffic emitted by Isaac Launchable. By extracting credentials, tokens, or workload payloads from the captured stream - and, per NVIDIA's impact statement, potentially tampering with them in transit - they pivot to executing code on the launcher host or exfiltrating sensitive robotics workload data. No public POC has been identified at time of analysis, and SSVC rates the issue as not automatable.