Answer in brief
CVE-2025-71348 records a High severity (CVSS 8.1) vulnerability in picklescan - Arbitrary Code Execution via torch.utils._config_module.load_config Bypass. The current sources do not mark it as known exploited. The current feed maps picklescan/picklescan (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps picklescan/picklescan (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| picklescan/picklescangeneric | >=0 <0.0.28 | 0.0.28 |
Published upstream
Jun 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 21, 2026
picklescan before 0.0.28 fails to detect malicious pickle files that invoke torch.utils._config_module.load_config function within reduce methods. Attackers can craft pickle files embedding arbitrary code that evades detection but executes during pickle.load, enabling remote code execution in supply chain attacks.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-71348 records a High severity (CVSS 8.1) vulnerability in picklescan - Arbitrary Code Execution via torch.utils._config_module.load_config Bypass. The current sources do not mark it as known exploited. The current feed maps picklescan/picklescan (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps picklescan/picklescan (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| picklescan/picklescangeneric | >=0 <0.0.28 | 0.0.28 |
Published upstream
Jun 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 21, 2026
picklescan before 0.0.28 fails to detect malicious pickle files that invoke torch.utils._config_module.load_config function within reduce methods. Attackers can craft pickle files embedding arbitrary code that evades detection but executes during pickle.load, enabling remote code execution in supply chain attacks.
Quoted source text, attributed separately from HOL analysis.