# CVE-2026-94092: dmlc dgl utils.py _read_torch_data deserialization

> Remote attackers can execute arbitrary code via unsafe deserialization in the DGL library's data loading function.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-jf58-7v68-wxqh

## What is CVE-2026-94092?

CVE-2026-94092 is a medium-severity unsafe deserialization vulnerability in dmlc dgl, published on 20 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was detected in dmlc dgl up to 2.1.0. This impacts the function load_info/_read_torch_data of the file utils.py. Performing a manipulation of the argument path results in deserialization. The attack can be initiated remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-94092 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94092 is a medium-severity unsafe deserialization vulnerability in dmlc dgl, published on 20 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-94092 exists.

Affected product: dmlc dgl. 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-94092/ (Markdown: https://insights.sbomify.com/CVE-2026-94092/index.md)
```

## Sources

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

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