# CVE-2024-37065: Skops unsafe deserialization

> Attackers can execute arbitrary code by tricking users into loading maliciously crafted models in the skops Python library.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-q49c-6v6g-wgq3, PYSEC-2026-1928

## What is CVE-2024-37065?

CVE-2024-37065 is a high-severity unsafe deserialization vulnerability in Skops-dev Skops, published on 4 Jun 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-37065?

3 open source packages ship an affected version, including skops.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `skops` | PyPI | From 0.6 to 0.9 | None |
| `skops` | PyPI | From 0.6 to 0.9 | None |
| `skops` | PyPI | From 0.6 to 0.9 | None |

## How do I fix CVE-2024-37065?

No fix has been published for CVE-2024-37065 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-37065 being exploited?

There is no known exploitation of CVE-2024-37065 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37065 and fix it if it is affected.

What it is: CVE-2024-37065 is a high-severity unsafe deserialization vulnerability in Skops-dev Skops, published on 4 Jun 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-37065 in the wild and no public exploit code.

Affected packages and fixed versions:
- skops (PyPI): affected from 0.6 up to 0.9; no fix listed
- skops (PyPI): affected from 0.6 up to 0.9; no fix listed
- skops (PyPI): affected from 0.6 up to 0.9; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-37065/ (Markdown: https://insights.sbomify.com/CVE-2024-37065/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-37065
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-37065
- OSV: https://osv.dev/vulnerability/CVE-2024-37065

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-37065/
Summaries are generated and may contain mistakes; the official description above is the record.