Code execution via unsafe pickle loading
Published Sep 20, 2026 · Updated Sep 20, 2026
Unsafe deserialization in DGL 2.0 and 2.1.0 allows remote authenticated users to execute code through a crafted data-file load. The load_info path passes file content directly to pickle.load, while _read_torch_data forces torch.load to use weights_only=False. Exploitation requires low-privileged remote access and user action that causes the application to load the attacker's file; code runs with the loading process's privileges.
Summary
What happened
Unsafe deserialization in DGL 2.0 and 2.1.0 allows remote authenticated users to execute code through a crafted data-file load. The load_info path passes file content directly to pickle.load, while _read_torch_data forces torch.load to use weights_only=False. Exploitation requires low-privileged remote access and user action that causes the application to load the attacker's file; code runs with the loading process's privileges.
The record
- CVE
- CVE-2026-94092
- Published
- Sep 20, 2026
- Updated
- Sep 20, 2026
- Vendor
- Distributed (Deep) Machine Learning Community
- Product
- Deep Graph Library (DGL)
- Classifications
- CWE-502, CWE-20, T1204.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 20, 2026CVE publishedPublication date reported by the CVE source.
- Sep 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0
- Affected versionversion=2.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- DGL unsafe-deserialization proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started