Security readout for executives and security teams
Plain-English summary
This flaw weakens a safety tool used to detect dangerous Python pickle files. A malicious pickle can pass picklescan checks and still run commands when someone later loads it. The business risk is highest where teams exchange or ingest ML models, datasets, or artifacts from outside trusted build paths.
Executive priority
Prioritize remediation where picklescan protects ML artifact intake or third-party pickle files. This is high severity, but not currently cited as actively exploited in the provided sources.
Technical view
picklescan before 0.0.29 reportedly misses pickle reduce methods using idlelib.calltip.get_entity. The issue maps to CWE-502 and has CVSS 8.1. Successful impact requires a victim to load the malicious pickle after it was not flagged, enabling command execution with confidentiality and integrity impact.
Likely exposure
Exposure is likely in Python, ML, and data-science pipelines that use picklescan to vet pickle-based artifacts before loading them. Internet exposure is indirect; the dangerous action is loading a crafted file, not merely running a public service.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation. The scenario is plausible supply-chain or artifact-poisoning abuse: an attacker supplies a pickle that bypasses scanning, then code runs when a victim loads it.
Researcher notes
The supplied evidence identifies the bypass primitive and affected range, but does not include full patch details, exploit telemetry, or product CPEs. Avoid assuming all pickle scanners are affected; scope specifically to picklescan and the cited advisory versions.
Mitigation direction
- Upgrade picklescan to 0.0.29 or later where vendor guidance supports it.
- Do not load pickle files from untrusted or unauthenticated sources.
- Treat picklescan as one control, not a guarantee of pickle safety.
- Quarantine and re-review pickle artifacts accepted by older picklescan versions.
- Monitor the GitHub advisory for additional vendor guidance.
Validation and detection
- Inventory all environments using picklescan and record installed versions.
- Find pipelines that scan pickle, model, or dataset artifacts before loading them.
- Confirm whether artifacts accepted by picklescan are later executed or deserialized.
- Review dependency lockfiles and container images for picklescan before 0.0.29.
- Check whether external artifact ingestion has provenance and approval controls.
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-71360 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-9xph-j2h6-g47v)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: picklescan - Remote Code Execution via Undetected idlelib.calltip.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.