Security readout for executives and security teams
Plain-English summary
CVE-2025-71370 affects picklescan, a tool used to inspect Python pickle files for unsafe content. Versions before 0.0.28 can miss a malicious PyTorch-related function call. If a user or system trusts that scan result and later loads the pickle file, attacker-supplied code may run.
Executive priority
Prioritize remediation for ML and data pipelines that accept external artifacts. The business risk is unauthorized code execution from a file that security tooling may incorrectly classify as safe. Upgrade quickly and reduce reliance on pickle for untrusted content.
Technical view
picklescan before 0.0.28 fails to detect malicious torch.jit.unsupported_tensor_ops.execWrapper calls embedded in pickle files. This is a CWE-502 unsafe deserialization detection bypass. The reported impact is arbitrary code execution when the crafted pickle is loaded with pickle.load(), with CVSS 3.1 score 8.1 and user interaction required.
Likely exposure
Exposure is most likely in ML, data science, or model-ingestion workflows that use picklescan to assess untrusted pickle files before loading them. Risk increases where external model artifacts, datasets, or serialized Python objects are accepted from users, partners, repositories, or automated pipelines.
Exploitation context
The cited sources describe a crafted pickle file that bypasses picklescan detection and executes code only when loaded. The source bundle does not indicate CISA KEV listing or confirmed active exploitation. This is still high impact because pickle loading is inherently dangerous when files are untrusted.
Researcher notes
This issue is a scanner bypass leading to downstream RCE when pickle.load() processes the malicious file. It is not described as remote compromise without user or workflow interaction. No active exploitation is supported by the provided KEV flag or cited sources.
Mitigation direction
- Upgrade picklescan to version 0.0.28 or later.
- Do not load untrusted pickle files solely because picklescan reports them clean.
- Review vendor advisory guidance for any additional remediation details.
- Prefer safer serialization formats where pickle functionality is not required.
Validation and detection
- Inventory systems and pipelines using picklescan.
- Confirm deployed picklescan versions are 0.0.28 or later.
- Identify workflows that load pickle files from external or untrusted sources.
- Review recent accepted pickle artifacts for provenance and business necessity.
- Verify policy blocks unsafe pickle loading in high-risk ingestion paths.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-71370 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N2.85.2VulnCheckCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7.6HighVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-vr7h-p6mm-wpmh)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: picklescan - Remote Code Execution via torch.jit.unsupported_tensor_ops.execWrapperCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.