# CVE-2026-108945: iMoonLab yolov13 AutoBackend Model Loading autobackend.py eval code injection

> Local attackers can execute arbitrary code via eval injection in AutoBackend model loading when manipulating specific arguments.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-qmg4-358m-mfg3

## What is CVE-2026-108945?

CVE-2026-108945 is a medium-severity code injection vulnerability in iMoonLab yolov13, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was detected in iMoonLab yolov13 up to 73289949533efac82bb5f72ec19b746618656bd2. Affected by this issue is the function eval of the file ultralytics/nn/autobackend.py of the component AutoBackend Model Loading. Performing a manipulation of the argument imgsz/names/kpt_shape results in code injection. The attack must be initiated from a local position. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-108945?


## How do I fix CVE-2026-108945?

No fix has been published for CVE-2026-108945 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108945 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108945 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108945 and fix it if it is affected.

What it is: CVE-2026-108945 is a medium-severity code injection vulnerability in iMoonLab yolov13, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108945 exists.

Affected product: iMoonLab yolov13. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-108945/ (Markdown: https://insights.sbomify.com/CVE-2026-108945/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-108945
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108945
- OSV: https://osv.dev/vulnerability/CVE-2026-108945

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-108945/
Summaries are generated and may contain mistakes; the official description above is the record.