CVE-2026-118615

Read full description

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.

CVSS 7.8 (HIGH)

Attention and evidence

HYPE SCORE

0.6/10

REALITY · THREAT PRIORITY

2.7/10

General review priority; not probability

Evidence confidence: Insufficient evidence

Why this priority?

Technical severity: CVSS 7.8: +2.73
Fresh EPSS: 0.41%: +0.01

General review priority, not probability, victim count or asset-specific risk. A range covers missing CVSS/EPSS inputs within the current evidence state.

Sources: 2 documents and public datasets.

Hype components

Headline sample (25%)

10/100

Press, 30 days (60%)

5/100

Grounded branding (15%)

0/100

HYPE TOTAL6/100

Sources and documents

ZDI: Published Advisories

Technical advisory · 28 Oct 2026, 05:00 · ZDI-26-814: (0Day) Ultralytics torch_safe_load Command Injection Remote Code Execution Vulnerability

ZDI: Published Advisories

Press · 28 Oct 2026, 05:00 · ZDI-26-814: (0Day) Ultralytics torch_safe_load Command Injection Remote Code Execution Vulnerability

Score evolution

● Hype ● Reality

Earlier evidence-support scores are retained in history; this chart shows only the current priority definition.

First record: hype 0.6 · reality 2.7 (2026-11-02 15:14). The curve appears once the score changes.

Public exploit evidence

Public exploit entries / repo candidates

Evidence context and dated references

Reality is general threat/review priority, combining observed exploitation, CVSS severity and fresh EPSS. Evidence confidence is separate. This is not calibrated risk, a victim count or an asset-specific assessment. A range reflects missing numeric inputs. Published 8 days ago. Exploitation evidence usually takes weeks to show up: a low reality score can mean there is no data yet, not that the flaw is mild.

Evidence in context

Confidence in exploitation evidence: Insufficient evidence
Priority basis: Exploitation in attacks unconfirmed; CVSS 7.8; EPSS 0.4%
Attention, last 30 days: 1 distinct story titles; 1 press documents; 1 publisher domains.
Technical potential: local access, no prior privileges, user interaction.
Observed activity: No exploitation observation is recorded.
Known scale: Not quantified.
Evidence confidence basis: Insufficient evidence

Score evaluated: 2026-11-05 13:59:55.835577+00:00 · EPSS snapshot: 2026-11-05T12:03:04Z

Source event timeline

First press mention

28 Oct 2026, 05:00

Latest press mention

28 Oct 2026, 05:00

Published

28 Oct 2026, 16:54

Score calculated

05 Nov 2026, 13:59