Security readout for executives and security teams
Plain-English summary
This flaw affects picklescan, a tool meant to detect unsafe Python pickle files. Versions before 0.0.28 can miss a malicious pickle technique involving PyTorch internals. If someone later loads that pickle, embedded commands may run. The main business risk is misplaced trust in a scan result for ML or Python artifacts.
Executive priority
Treat this as high priority for teams handling ML models or Python serialized artifacts. The vulnerability weakens a safety control and can lead to command execution if unsafe artifacts are loaded. Prioritize upgrade and workflow review over broad emergency response unless exposed deserialization paths exist.
Technical view
CVE-2025-71353 is a CWE-502 deserialization detection bypass in picklescan before 0.0.28. Malicious pickle content using torch._dynamo.guards.GuardBuilder.get in reduce methods can evade detection and execute arbitrary commands when deserialized. CVSS 3.1 is 8.1, with network attack vector and required user interaction.
Likely exposure
Exposure is most likely in ML, data science, or CI pipelines that scan pickle, model, or artifact files with vulnerable picklescan versions, then deserialize files based on scan results. Systems that do not use picklescan or do not load pickle files are not indicated as exposed by the bundle.
Exploitation context
The bundle describes attacker-crafted pickle files that evade detection and execute when loaded. It does not cite active exploitation, and KEV status is false. Practical exploitation still depends on a victim workflow accepting and loading a malicious pickle after relying on a vulnerable scan result.
Researcher notes
The key issue is not that picklescan executes code directly, but that it can fail to flag a malicious pickle pattern. Evidence provided identifies affected versions as before 0.0.28 and names the PyTorch GuardBuilder.get reduce-method technique. No exploit-in-the-wild evidence is included.
Mitigation direction
- Upgrade picklescan to 0.0.28 or later where used.
- Do not load untrusted pickle files, even after scanning.
- Add sandboxing around pickle deserialization workflows.
- Review vendor advisories before relying on scanner coverage.
- Re-scan stored pickle artifacts after upgrading.
Validation and detection
- Inventory environments using picklescan and record versions.
- Identify workflows that deserialize pickle files after scanning.
- Check CI, model registry, and notebook pipelines for pickle handling.
- Confirm vulnerable versions are removed from lockfiles and images.
- Review logs for unexpected pickle artifact ingestion.
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-71353 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-86cj-95qr-2p4f)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: picklescan - Remote Code Execution via torch._dynamo.guards.GuardBuilder.getCVE 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.