Security readout for executives and security teams
Plain-English summary
This issue affects picklescan, a tool intended to detect risky Python pickle files. Versions before 0.0.29 can miss a dangerous built-in Python function used inside pickle reduce methods. If an organization trusts that scan result and later deserializes a malicious pickle, arbitrary code could run.
Executive priority
Prioritize remediation where pickle files enter production, CI, model, or data pipelines from outside trusted teams. The business risk is high because a security control may falsely approve dangerous files, enabling code execution later.
Technical view
CVE-2025-71374 is a CWE-502 deserialization detection bypass in picklescan before 0.0.29. The scanner fails to detect profile.Profile.run in pickle reduce methods. The CVSS 3.1 score is 8.1, with network attack vector, low complexity, no privileges, and required user interaction.
Likely exposure
Exposure is most likely in ML, data science, CI, or ingestion workflows that scan externally supplied pickle artifacts with vulnerable picklescan versions and then deserialize artifacts considered clean.
Exploitation context
The sources describe remote attackers crafting malicious pickle files that bypass picklescan detection and lead to code execution when deserialized. The provided bundle does not show KEV listing or confirmed active exploitation.
Researcher notes
Evidence is limited to the CVE record, GitHub advisory, and VulnCheck advisory in the supplied bundle. The affected condition is specific: undetected profile.Profile.run use in pickle reduce methods. No exploit-in-the-wild evidence was provided.
Mitigation direction
- Upgrade picklescan to 0.0.29 or later.
- Avoid deserializing pickle files from untrusted or unauthenticated sources.
- Treat prior clean scan results from vulnerable versions as unreliable.
- Check vendor guidance for any additional remediation or detection advice.
- Restrict artifact ingestion paths that can introduce pickle files.
Validation and detection
- Inventory picklescan versions across repositories, CI images, and runtime environments.
- Identify workflows that scan or deserialize pickle files.
- Re-scan relevant pickle artifacts after upgrading picklescan.
- Review dependency lockfiles and container images for vulnerable versions.
- Confirm controls block untrusted pickle deserialization where possible.
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-71374 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-x696-vm39-cp64)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: picklescan - Arbitrary Code Execution via Undetected profile.Profile.runCVE 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.