← Back
CVE-2025-54886
Unsafe Deserialization in skops (CVE-2025-54886)
Summary
vulnerability in skops (CVE-2025-54886). Successful exploitation can lead to full system takeover. Exploitable via ``Card``. Mitigation: upgrade to `0.13.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-54886** has been found in skops.
Attackers can target a specific entry point like ``Card`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade skops to **0.13.0** or later.
If unsure, ask your IT team or search "skops CVE-2025-54886" on the vendor's site.
CVE-2025-54886 (skops) — CWE-502 /
Attack vector: local / unauthenticated / no user interaction
Attack surface: `Card` / `skops` / `Card.get_model` / `joblib`
Patched: `0.13.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**unsafe deserialization** (CWE-502) exists in skops. Attackers reach the vulnerable code path via ``Card`` without authentication.
📍 Affected scope
skops — . Attack surface: `Card` / `skops` / `Card.get_model` / `joblib`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.13.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'skops' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'skops' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `skops` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade skops to 0.13.0ステージング環境で 0.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
skops
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.13.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-54886
- advisory https://github.com/advisories/GHSA-378x-6p4f-8jgm
- package https://github.com/skops-dev/skops
- package https://pypi.org/project/skops
- web https://github.com/skops-dev/skops/security/advisories/GHSA-378x-6p4f-8jgm
- web https://github.com/skops-dev/skops/commit/29d61ea8a92f2bde6830e8f32cc72a1a87211cda
- web https://github.com/io-no/CVE-Reports/tree/main/CVE-2025-54886