CVE-2026-94092

Received Received - Intake

Deserialization Flaw in DGL up to 2.1.0

Publication date: 2026-09-20

Last updated on: 2026-09-20

Assigner: VulDB

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-20

Last Modified

2026-09-20

Generated

2026-09-21

AI Q&A

2026-09-21

EPSS Evaluated

N/A

NVD

CVE-2026-94092

EUVD

EUVD-2026-83796

Affected Vendors & Products

Vendor	Product	Version / Range
dmlc	dgl	to 2.1.0 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-502	The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
CWE-20	The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

Attack-Flow Graph

Executive Summary

This vulnerability exists in dmlc dgl versions up to 2.1.0, specifically in the load_info/_read_torch_data function of utils.py. An attacker can remotely manipulate the path argument to trigger deserialization, potentially leading to unauthorized actions or data access.

Impact Analysis

The vulnerability allows remote attackers to execute deserialization attacks, which may lead to code execution, data breaches, or system compromise. It requires some privileges but can be exploited over a network.

Compliance Impact

This vulnerability involves deserialization of manipulated data, which could lead to unauthorized code execution or data breaches. Such risks may impact compliance with GDPR (data protection) and HIPAA (health data security) by exposing sensitive information or violating integrity requirements.

Mitigation Strategies

Immediately update dgl to a version beyond 2.1.0 if available. If no update exists, disable the load_info/_read_torch_data function in utils.py or restrict access to the system to trusted users only. Monitor for unusual deserialization activity in logs.

Hi! I’m here to help you understand CVE-2026-94092. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70