Answer in brief
CVE-2025-71372 records a High severity (CVSS 8.1) vulnerability in Picklescan - Arbitrary Code Execution via numpy.f2py.crackfortran.getlincoef Gadget. 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.33 | 0.0.33 |
Published upstream
Jul 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 4, 2026
Picklescan before 0.0.33 fails to detect the numpy.f2py.crackfortran.getlincoef gadget in pickle __reduce__ methods, allowing arbitrary code execution. Attackers can craft malicious pickle files that execute arbitrary Python code when loaded, bypassing Picklescan's safety checks and enabling supply-chain poisoning of shared model files.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-71372 records a High severity (CVSS 8.1) vulnerability in Picklescan - Arbitrary Code Execution via numpy.f2py.crackfortran.getlincoef Gadget. 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.33 | 0.0.33 |
Published upstream
Jul 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 4, 2026
Picklescan before 0.0.33 fails to detect the numpy.f2py.crackfortran.getlincoef gadget in pickle __reduce__ methods, allowing arbitrary code execution. Attackers can craft malicious pickle files that execute arbitrary Python code when loaded, bypassing Picklescan's safety checks and enabling supply-chain poisoning of shared model files.
Quoted source text, attributed separately from HOL analysis.