Security readout for executives and security teams
Plain-English summary
CVE-2025-71347 is a bypass in picklescan before 0.0.33. A malicious pickle file can pass scanning and still execute code when an application later deserializes it. The business risk is highest where external pickle-based ML artifacts or data files are accepted and trusted after scanning.
Executive priority
Prioritize remediation where picklescan gates externally supplied ML or data artifacts. The vulnerability can turn a failed security check into code execution during later processing, but current provided sources do not show active exploitation.
Technical view
picklescan failed to detect dangerous use of numpy.f2py.crackfortran.param_eval in pickle reduce methods. This maps to CWE-502: unsafe deserialization. The provided CVSS is 8.1, network exploitable with low attack complexity, no privileges required, and user interaction required.
Likely exposure
Exposure is likely limited to environments using picklescan before 0.0.33 to inspect untrusted pickle files before loading them. ML platforms, model registries, data science workflows, and automated artifact ingestion pipelines are plausible exposure points if they deserialize scanned pickle content.
Exploitation context
The source bundle does not cite active exploitation and KEV status is false. Exploitation depends on getting a target workflow to process a malicious pickle file that bypasses picklescan and is later deserialized by an application.
Researcher notes
Focus validation on deserialization trust boundaries, not only package presence. The affected behavior involves missed detection of a specific callable pattern in reduce methods. Do not assume all pickle defenses are bypassed; confirm whether picklescan is in the enforcement path.
Mitigation direction
- Upgrade picklescan to version 0.0.33 or later.
- Avoid deserializing pickle files from untrusted or unauthenticated sources.
- Treat scanner approval as insufficient for pickle safety.
- Review vendor advisory guidance for any additional fixed-version details.
- Restrict artifact ingestion paths that accept pickle-based files.
Validation and detection
- Inventory systems and pipelines using picklescan.
- Confirm deployed picklescan versions are 0.0.33 or later.
- Identify workflows that deserialize pickle files after scanning.
- Review ingestion logs for externally supplied pickle artifacts.
- Check dependency manifests, container images, and CI environments.
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-71347 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-cffc-mxrf-mhh4)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: picklescan - Undetected Remote Code Execution via numpy.f2py.crackfortran.param_evalCVE 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.