dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-37065

HIGH · 7.8 CVSS v3.1 Published 2024-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Deserialization of untrusted data can occur in versions 0.6 or newer of the skops python library, enabling a maliciously crafted model to run arbitrary code on an end user's system when loaded.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The skops Python library versions 0.6 and newer insecurely deserializes untrusted data, allowing attackers to embed malicious code in crafted model files that executes arbitrary commands on the victim's system when the model is loaded.

MitigationAvoid loading skops models from untrusted sources. Monitor for available patches from the skops maintainers and update promptly. Consider implementing model signing/verification if supported.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if skops is installed
    Run 'pip show skops' or 'pip list | grep skops' in your Python environment
    Affected if skops package is installed and version is 0.6 or newer
  2. Verify the installed skops version
    Run 'python -c "import skops; print(skops.__version__)"' to get the exact version number
    Affected if The version reported is 0.6 or any version higher (e.g., 0.7, 0.8, etc.)
  3. Identify skops model file loading in your code
    Search your codebase for calls to skops.io.load, skops.load, or similar loading functions that accept file paths (look for .skops file extensions in your project)
    Affected if Your code loads .skops model files using skops loading functions
  4. Determine source trust for loaded models
    Review where your skops model files originate - check if they come from user uploads, external URLs, unverified repositories, or untrusted network sources
    Affected if Models are loaded from untrusted or unverified sources such as user uploads, external URLs, or third-party repositories without verification

You are affected if skops version 0.6 or newer is installed AND your application loads .skops model files, especially from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid loading skops models from untrusted sources. Monitor for available patches from the skops maintainers and update promptly. Consider implementing model signing/verification if supported.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37065 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37065 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data