PyTorch Model Files Can Bypass Pickle Scanners via Unexpected Pickle Extensions

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-1716: 1.72% estimated exploitation activity in the next 30 days; percentile 77.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
• CVE-2025-1889: 0.40% estimated exploitation activity in the next 30 days; percentile 33.79 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

CVE-2025-1889

Summary Picklescan fails to detect hidden pickle files embedded in PyTorch model archives due to its reliance on file extensions for detection. This allows an attacker to embed a secondary, malicious pickle file with a non-standard extension inside a model archive, which remains undetected by picklescan but is still loaded by PyTorch's torch.load() function. This can lead to arbitrary code execution when the model is loaded.

Details Picklescan primarily identifies pickle files by their extensions (e.g., .pkl, .pt). However, PyTorch allows specifying an alternative pickle file inside a model archive using the pickle_file parameter when calling torch.load(). This makes it possible to embed a malicious pickle file (e.g., config.p) inside the model while keeping the primary data.pkl file benign. A typical attack works as follows: - A PyTorch model (model.pt) is created and saved normally. - A second pickle file (config.p) containing a malicious payload is…

Published by the source

3 Mar 2025, 20:05 UTC

Last modified by the source

9 Apr 2025, 17:59 UTC

Source last checked

25 Oct 2026, 01:37 UTC

1. Revision 3 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-769v-p64c-89pr

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-655q-fx9r-782v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-1716

Advisory: PyTorch Model Files Can Bypass Pickle Scanners via Unexpected Pickle Extensions
IDs: CVE-2025-1716, GHSA-655q-fx9r-782v
Record: https://patchnext.com/advisories/cve-2025-1716 (revision 3, source checked 25 Oct 2026, 01:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: picklescan 0.0.22. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI picklescan: affected < 0.0.22; fixed in 0.0.22

## Suggested inspection (read-only)
- `python -m pip show picklescan`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on picklescan.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-655q-fx9r-782v (OSV record GHSA-655q-fx9r-782v lists affected ranges: PyPI picklescan >=0 <0.0.22 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-769v-p64c-89pr (OSV record GHSA-769v-p64c-89pr lists affected ranges: PyPI picklescan >=0 <0.0.22 (fixed))

Commands are suggestions: review each one before running it.