NVIDIA Isaac-GR00T for all platforms には、Python コンポーネントに脆弱性が存在し、攻撃者がコードインジェクションを引き起こす可能性があります。この脆弱性の悪用により、コード

The code injection vulnerability in NVIDIA Isaac-GR00T allows an attacker to inject and execute malicious code within the Python component. This could lead to a wide range of impacts, including complete system compromise. An attacker could gain unauthorized access to sensitive data, modify system configurations, and potentially establish persistent access. The potential for privilege escalation is significant, as the injected code could be executed with the privileges of the Isaac-GR00T process. Data tampering could corrupt training datasets or deployed models, leading to unpredictable robot behavior. The blast radius extends to any system utilizing vulnerable versions of Isaac-GR00T, particularly those involved in critical robotics applications.

Robotics developers and engineers utilizing NVIDIA Isaac-GR00T are at risk. Organizations deploying Isaac-GR00T in production environments, particularly those involving autonomous systems or critical infrastructure, face a heightened risk. Those using older, unpatched versions of Isaac-GR00T are most vulnerable.

• windows / supply-chain:

Get-Process | Where-Object {$_.ProcessName -like '*isaac-gr00t*'}

• linux / server:

ps aux | grep isaac-gr00t

• python:

import os
import sys
print(sys.version)

• generic web: Check for unusual file uploads or modifications to Python scripts within the Isaac-GR00T environment.

1. 2025-08-13Disclosure

   disclosure

1. 予約済み2025-01-14
2. 公開日2025-08-13
3. EPSS 更新日2026-03-23

The primary mitigation for CVE-2025-23296 is to upgrade to version 9ca97e1 or later. If immediate upgrading is not feasible, consider implementing strict input validation on any data passed to the vulnerable Python component. This can help prevent malicious code from being injected. Review and restrict access to the Python component to only authorized users and processes. Monitor system logs for any unusual activity or attempts to exploit the vulnerability. While a WAF is unlikely to directly mitigate this code injection, it can help detect and block suspicious requests targeting the vulnerable component. After upgrading, confirm the fix by attempting to trigger the code injection vulnerability with known payloads and verifying that they are blocked.