Quick answers
- Is CVE-2025-54886 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-54886 being exploited in the wild.
- How severe is CVE-2025-54886?
- Low severity, with a CVSS score of 3.1, published 7 July 2026.
- Which products and versions are affected?
- skops (PyPI) ECOSYSTEM:introduced=0,fixed=0.13.0.
- Is there a fix for CVE-2025-54886?
- Yes. skops (PyPI): upgrade to 0.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-54886 attacked?
- It is attacked with local access.
- Am I affected by CVE-2025-54886?
- Check whether you run skops (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- skops (PyPI): upgrade to 0.13.0 or later
pip install "skops>=0.13.0"
Technical details
This is a deserialization vulnerability (CWE-502) in the SKOPS Card class's get_model method. When a file is not recognized as a ZIP archive, the code silently invokes joblib.load() instead of SKOPS' secure load() function. Unlike SKOPS, joblib allows unrestricted pickle deserialization, enabling arbitrary code execution. The vulnerability is triggered automatically during Card instantiation (not requiring explicit get_model calls), with no authentication or user interaction needed. An attacker can distribute a malicious file with a .skops extension that is actually a pickle-serialized object. The vulnerability affects all versions before 0.13.0 and is fixed in version 0.13.0 and later.
Affected products
- SKOPS SKOPS <0.13.0
Identifiers
- CVE-2025-54886
- GHSA-378x-6p4f-8jgm
- PYSEC-2026-1925
Timeline
- 2025-08-07: disclosed
- 2025-08-07: patched: Fixed in version 0.13.0