Security readout for executives and security teams
Plain-English summary
This flaw affects organizations that use picklescan to screen Python pickle files before loading them. A malicious pickle could pass scanning because a dangerous doctest function was not detected, then run code when another process loads it. The business risk is highest where untrusted model, data, or artifact files are accepted from outside parties.
Executive priority
Prioritize this for teams handling external ML models, datasets, or serialized Python artifacts. It is not listed as actively exploited in the provided sources, but the impact is high because a trusted scanning control can fail before code execution.
Technical view
picklescan before 0.0.30 did not detect doctest.debug_script in pickle analysis. The CVE describes a CWE-502 deserialization risk: a crafted pickle can evade picklescan detection and execute arbitrary commands when pickle.load is later invoked. CVSS 3.1 is 8.1, with network attack vector, low complexity, no privileges, and required user interaction.
Likely exposure
Exposure is likely in ML, data science, CI, or artifact-ingestion workflows that rely on picklescan as a gate before loading pickle files. Systems that never process untrusted pickle files have lower practical exposure.
Exploitation context
The bundle does not show KEV listing or confirmed active exploitation. Exploitation requires a target workflow to receive a malicious pickle and later load it. The source bundle supports bypass and code execution risk, but not public weaponization status.
Researcher notes
Focus validation on trust boundaries around pickle ingestion, not only package presence. The key evidence is a missed dangerous global involving doctest.debug_script. The record supports arbitrary code execution on later deserialization, but does not provide exploit-in-the-wild evidence.
Mitigation direction
- Upgrade picklescan to 0.0.30 or later per vendor guidance.
- Avoid loading pickle files from untrusted or unauthenticated sources.
- Treat prior picklescan approvals of external pickle files as unreliable.
- Add policy controls for model and artifact provenance.
- Check vendor advisories for any additional fix guidance.
Validation and detection
- Inventory systems and pipelines that install or invoke picklescan.
- Confirm deployed picklescan versions are not earlier than 0.0.30.
- Identify workflows that call pickle.load on externally supplied files.
- Review recent accepted pickle artifacts from untrusted sources.
- Verify dependency lockfiles and container images include the fixed version.
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-71368 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-fqq6-7vqf-w3fg)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: picklescan - Arbitrary Code Execution via Undetected doctest.debug_scriptCVE 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.