THU-MIG yoloe up to 40cd606cabdbe2b566d6f14a6b162c89206e9a1b AutoBackend Model Loading autobackend.py eval imgsz/names/kpt_shape eval injection

Summaryinfo

A vulnerability was found in THU-MIG yoloe up to 40cd606cabdbe2b566d6f14a6b162c89206e9a1b. It has been classified as problematic. This impacts the function eval of the file ultralytics/nn/autobackend.py of the component AutoBackend Model Loading. This manipulation of the argument imgsz/names/kpt_shape causes eval injection. This vulnerability appears as CVE-2026-111865. The attack requires local access. In addition, an exploit is available. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.

Detailsinfo

A vulnerability has been found in THU-MIG yoloe up to 40cd606cabdbe2b566d6f14a6b162c89206e9a1b and classified as problematic. Affected by this vulnerability is the function eval of the file ultralytics/nn/autobackend.py of the component AutoBackend Model Loading. The manipulation of the argument imgsz/names/kpt_shape with an unknown input leads to a eval injection vulnerability. The CWE definition for the vulnerability is CWE-95. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval"). As an impact it is known to affect confidentiality, integrity, and availability.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-111865. The exploitation appears to be easy. An attack has to be approached locally. Technical details and also a public exploit are known.

It is possible to download the exploit at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• THU-MIG

Name

• yoloe

Version

• 40cd606cabdbe2b566d6f14a6b162c89206e9a1b

Website

• Product: https://github.com/THU-MIG/yoloe/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #1004883: THU-MIG yoloe up to main commit 40cd606cabdbe2b566d6f14a6b162c89206e9a1b (vendors ultralytics 8.3.39) Code Injection (by Dem00000)

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion