Security readout for executives and security teams
Plain-English summary
CVE-2025-71358 affects picklescan, a tool used to inspect Python pickle files. Versions before 0.0.29 may miss malicious pickle content that can run arbitrary commands when a victim later loads the file. The main business risk is misplaced trust in a scan result for untrusted pickle or model artifacts.
Executive priority
Prioritize remediation if the organization handles external pickle, ML model, or Python artifact files. The issue is high severity because it weakens a safety control and can lead to command execution after a user loads a malicious file.
Technical view
picklescan fails to detect pickle reduce-method abuse involving idlelib.autocomplete.AutoComplete.get_entity. The vulnerability maps to CWE-502 and can allow arbitrary command execution during pickle.load() after user interaction. The reported CVSS is 8.1, network attack vector, low complexity, no privileges, and required user interaction.
Likely exposure
Exposure is likely where teams accept, download, scan, or exchange pickle-based artifacts and then load them in Python workflows. The source bundle only names picklescan as affected; it does not establish exposure for other products or platforms.
Exploitation context
The advisory describes malicious pickle files that evade picklescan detection and execute when loaded by a victim. KEV is false in the bundle, and no cited source here confirms active exploitation in the wild.
Researcher notes
Evidence is limited to the supplied CVE, GitHub advisory reference, and VulnCheck reference. The vulnerable behavior is detection bypass for a pickle deserialization gadget path, not a direct remote service exploit. User interaction is required because execution occurs when the victim loads the pickle.
Mitigation direction
- Identify all environments using picklescan.
- Move off picklescan versions before 0.0.29 where applicable.
- Check the GitHub advisory for confirmed fixed-version guidance.
- Avoid loading pickle files from untrusted sources.
- Treat prior clean picklescan results as insufficient for untrusted artifacts.
Validation and detection
- Inventory dependency manifests and build images for picklescan usage.
- Confirm the deployed picklescan version in CI and analyst workstations.
- Review workflows that load pickle files after scanning.
- Reassess recently accepted pickle artifacts from untrusted sources.
- Check vendor advisory updates for detection or remediation changes.
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-71358 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-6w4w-5w54-rjvr)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: picklescan - Remote Code Execution via idlelib.autocomplete.AutoComplete.get_entityCVE 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.