Live › vulnerability › CVE-2026-118615
Go to dashboardThe torch_safe_load function in Ultralytics passes a user-supplied string into a system call without validating it. An attacker who gets a user to open a malicious file or visit a malicious page can run code as that user.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 17:34 UTC. All times on this page are UTC.
Teams that run Ultralytics and let the torch_safe_load path handle files or strings from outside users, such as uploaded model files or user-supplied paths. Systems that only load trusted, locally built models are less exposed. The sources do not name the affected version range.
No product ranges from the sources yet.
pip show ultralyticstorch_safe_load and note where its input comes fromtorch_safe_loadEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Ultralytics torch_safe_load Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Ultralytics. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.
The specific flaw exists within the torch_safe_load function. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-30122.
This page as .md · .json · in your agent: get_signal("CVE-2026-118615")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.