Vulnerabilities in pkg:pypi/skops
PACKAGECVE-2025-54886 is a HIGH (CVSS 8.4) skops card.get_model happily allows arbitrary vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Skops libraries in the PyPI ecosystem. The issue involves skops card.get_model happily allows arbitrary code execution. Remediation is available by upgrading affected packages to version 0.13.0.
pkg:pypi/skops
Vulnerability advisories affecting package pkg:pypi/skops. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-378x-6p4f-8jgm | CVE-2025-54886 | HIGH | SKOPS Card.get_model happily allows arbitrary code execution |
| GHSA-4v6w-xpmh-gfgp | CVE-2025-54413 | HIGH | Skops may allow MethodNode to access unexpected object fields through dot notation, leading to arbitrary code execution at load time |
| GHSA-m7f4-hrc6-fwg3 | CVE-2025-54412 | HIGH | Skops has Inconsistent Trusted Type Validation that Enables Hidden `operator` Methods Execution |
| GHSA-q49c-6v6g-wgq3 | CVE-2024-37065 | HIGH | Skops unsafe deserialization |
CVE-2025-54886 at a Glance
Security Impact
CVSS: 8.4
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2025-54886
To remediate this vulnerability, upgrade all affected Skops dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install skops>=0.13.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show skops
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2025-54886, inspect your installed packages using pip:
pip show skops
Analyze the terminal output to locate any version of Skops in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.13.0), your application is affected.
Note: The pip show skops command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Skops, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-54886 Affected Skops Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
skops
|
PyPI |
< 0.13.0
|
0.13.0
|
References
Frequently Asked Questions
What is CVE-2025-54886?
Which Skops versions are affected?
What version fixes CVE-2025-54886?
Is skops affected?
What is the CVSS score of CVE-2025-54886?
What CWE is associated with CVE-2025-54886?
How can I check PyPI dependencies for CVE-2025-54886?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-378x-6p4f-8jgm",
"modified" : "2025-09-10T20:52:05Z",
"published" : "2025-08-07T16:42:54Z",
"aliases" : [ "CVE-2025-54886" ],
"summary" : "SKOPS Card.get_model happily allows arbitrary code execution",
"details" : "## Summary\n\nThe `Card` class of `skops`, used for model documentation and sharing, allows arbitrary code execution. When a file other than `.zip` is provided to the `Card` class during instantiation, the internally invoked `Card.get_model` method silently falls back to `joblib` without warning. Unlike the `.skops` zip-based format, `joblib` permits unrestricted code execution, hence bypassing the security measures of `skops` and enabling the execution of malicious code.\n\n\n## Details\n\nThe `Card` class supports loading the model linked to the card using the `get_model` method. When a `.skops` model is provided, it uses the `load` function from `skops`, which includes security mechanisms. The `Card` class also supports consistent management of the `trusted` list, which can be passed during instance creation. As expected, if a `.skops` model is provided without a `trusted` list and an untrusted type is encountered during loading, an error is raised. This behavior is consistent with the security principles of `skops`.\n\nThe problem arises when a file format other than `.zip` is provided. As shown in the code snippet below, in this case, the `joblib` library is used to load the model. This happens **silently**, without any warning or indication that `joblib` is being used. This is a significant security risk because `joblib` does not enforce the same security measures as `skops`, allowing arbitrary code execution.\n\n```python\n# from `card/_model_card.py:354-358`\ntry:\n if zipfile.is_zipfile(model_path):\n model = load(model_path, trusted=trusted)\n else:\n model = joblib.load(model_path)\n```\n\nTo increase the concern, `get_model` is actually called internally by `skops` during card creation, so the user does not need to call it explicitly—only to create the `Card` object passing a `joblib` file.\n\n## PoC\n\nConsider the following example:\n\n```python\nfrom skops.card import Card\n\ncard = Card(\"model.skops\")\n```\n\nAn attacker could share a `model.skops` file that, despite its name, is **not** a `.zip` file. In this case, the `joblib.load` function is called, allowing arbitrary code execution if the file is actually a pickle-like object. This is difficult for the user to detect, as the check is based on the file’s format, not its extension or name.\n\nThis vulnerability exists regardless of the `trusted` list provided (or omitted) during `Card` instance creation, and is unaffected by any other parameters. Moreover, it occurs at the time of `Card` instantiation.\n\n## Attack Scenario\n\nAn attacker can craft a malicious model file that, when used to instantiate a `Card` object, enables **arbitrary code** on the victim’s machine. This requires no user interaction beyond instantiating the `Card` object (not even explicit loading). Given that `skops` is often used in collaborative environments and is designed with security in mind, this vulnerability poses a significant threat.\n\n## Attachments\nThe complete PoC is available on GitHub at [io-no/CVE-2025-54886](https://github.com/io-no/CVE-Reports/tree/main/CVE-2025-54886).",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "skops"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.13.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/skops-dev/skops/security/advisories/GHSA-378x-6p4f-8jgm"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-54886"
}, {
"type" : "WEB",
"url" : "https://github.com/skops-dev/skops/commit/29d61ea8a92f2bde6830e8f32cc72a1a87211cda"
}, {
"type" : "WEB",
"url" : "https://github.com/io-no/CVE-Reports/tree/main/CVE-2025-54886"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/skops-dev/skops"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-502" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-08-07T16:42:54Z",
"nvd_published_at" : "2025-08-08T01:15:25Z"
}
}