Skip to main content
CVE-2025-10155VulnerabilityPublished

CVE-2025-10155: mmaitre314 picklescan · Improper Input Validation

Affects mmaitre314 picklescanSource CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
mmaitre314 picklescanAffected
  • =0
Fixed in–

AI-suggested

1. Immediate mitigation involves discontinuing the use of vulnerable picklescan versions (up to 0.0.30) until a patched release is available. 2. Implement strict file extension and content-type validation before processing pickle files, ensuring that files with PyTorch-related extensions are not automatically trusted. 3. Employ sandboxing or isolated environments for deserializing pickle files to contain potential malicious code execution. 4. Monitor network traffic and logs for unusual activity related to pickle file processing or unexpected file extensions. 5. Educate developers and data scientists about the risks of deserializing untrusted pickle files and encourage the use of safer serialization formats (e.g., JSON, protobuf) where feasible. 6. Apply network segmentation to limit exposure of systems handling pickle files. 7. Prepare incident response plans specifically addressing potential RCE attacks via deserialization vulnerabilities.

Description

An Improper Input Validation vulnerability in the scanning logic of mmaitre314 picklescan versions up to and including 0.0.30 allows a remote attacker to bypass pickle files security checks by supplying a standard pickle file with a PyTorch-related file extension. When the pickle file incorrectly considered safe is loaded, it can lead to the execution of malicious code.

References

Community reviews

Loading reviews…