Python CVE-2026-118619

Exploitation requires the Ultralytics application to perform a download from Google Drive using an attacker-influenced path that is not validated before file operations (CWE-22). The attack is gated by user interaction (UI:R): the victim must visit a malicious page or open a malicious file that drives this download. No authentication is required of the attacker (PR:N), and the scope is unchanged (S:U) - code runs as the current process. The principal limiting factors are the required user interaction and the need for the application to use the Google Drive download code path; the exact trigger mechanism beyond 'lack of path validation' is not detailed in the available sources.

Signals point to a genuine but interaction-gated priority rather than a drop-everything emergency. The CVSS 3.0 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) describes a network-reachable, low-complexity, unauthenticated flaw with full confidentiality, integrity and availability impact, but it is gated by UI:R - a user must visit a malicious page or open a malicious file, so there is no self-propagating or fully automatable path. The vuln.today decision label is 'this_week', consistent with a serious issue that is not flagged for immediate emergency action. No EPSS probability is supplied in the input, so exploitation likelihood cannot be quantified; no CISA KEV listing is present, so there is no public exploit identified at time of analysis. Credibility is high because the issue was reported through ZDI (ZDI-26-818 / ZDI-CAN-32376), a reputable coordinated-disclosure source, but the advisory is a write-up rather than verified working exploit code. The main caveat is missing data: affected/fixed versions are only a wildcard CPE (cpe:2.3:a:ultralytics:ultralytics:*), and no EPSS or vendor patch metadata is provided here - these should be verified against the ZDI advisory and the Ultralytics project before final triage.

An attacker crafts a malicious page or file that causes a victim's Ultralytics-based application to fetch an asset from Google Drive; the download handler fails to validate the user-supplied path, so a traversal sequence writes attacker-controlled content outside the intended directory. When that content is subsequently used, arbitrary code runs in the context of the current process. No public exploit was identified at time of analysis, though ZDI has published advisory ZDI-26-818 describing the flaw.