CVE-2026-118616

Ultralytics parse_model Code Injection Remote Code Execution Vulnerability

Published Oct 28, 2026 CVSS 3.0 · 7.8 High EPSS < 1% KEV · Not listed
Description
Ultralytics parse_model Code 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 parse_model function. The issue results from the lack of proper validation of a user-supplied string before using it to execute Python code. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-30123.

Analysis

AI-generated

Technical impact

The vulnerability lies in the Ultralytics parse_model function, which naively executes a user‑supplied string as Python code without proper validation. This flaw allows an attacker to run arbitrary code in the context of the current user, potentially giving them full control over an affected system. The impact is the execution of any code the attacker chooses, leading to compromise of confidentiality, integrity, and availability.

Affected Systems

Ultralytics’s Ultralytics product is affected. No specific version information is provided, so all releases that include the parse_model function are potentially vulnerable.

Risk and Exploitability

The CVSS score of 7.8 classifies this issue as high severity; EPSS data is unavailable, and the vulnerability is not listed in the CISA KEV catalog. The flaw requires user interaction: the target must view a malicious page or open a malicious file that triggers the parse_model call. Once triggered, the attacker can execute code with the privileges of the running user. The lack of input validation, identified as CWE‑94, makes the vulnerability exploitable with relatively low effort in environments where an attacker can supply input to the vulnerable function.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor’s patch or upgrade to a fixed version when it becomes available.
  • Restrict the parse_model function so that it only accepts trusted, sanitized input strings; validate all parameters to prevent code injection.
  • Limit user interaction with untrusted content by disabling or removing features that invoke parse_model, or by employing application restrictions such as element whitelisting.

Generated by OpenCVE AI on October 28, 2026 at 18:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Ultralytics
Ultralytics ultralytics
Vendors & Products Ultralytics
Ultralytics ultralytics
Type Values Removed Values Added
Description Ultralytics parse_model Code 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 parse_model function. The issue results from the lack of proper validation of a user-supplied string before using it to execute Python code. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-30123.
Title Ultralytics parse_model Code Injection Remote Code Execution Vulnerability
Weaknesses CWE-94
References
Metrics cvssV3_0

{'score': 7.8, 'vector': 'CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-94

    Improper Control of Generation of Code ('Code Injection')

Sources

Status
PUBLISHED
Assigner
zdi
Published
Updated
Nov 5, 2026, 5:08 PM
Reserved
Oct 28, 2026, 4:53 PM
Status
Awaiting Analysis
Published
Oct 28, 2026, 5:18 PM
Modified
Nov 5, 2026, 5:17 PM