# CVE-2024-37062: ydata unsafe deserialization

> Attackers can execute arbitrary code on user systems by tricking them into loading a maliciously crafted report generated by the ydata-profiling 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-fpvj-m2h6-6wc5, PYSEC-2026-2062

## What is CVE-2024-37062?

CVE-2024-37062 is a high-severity unsafe deserialization vulnerability in YdataAI ydata-profiling, 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 3.7.0 or newer of Ydata's ydata-profiling open-source library, enabling a malicously crafted report 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-37062?

3 open source packages ship an affected version, including ydata-profiling.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ydata-profiling` | PyPI | From 3.7.0 to 4.8.3 | None |
| `ydata-profiling` | PyPI | From 3.7.0 to 4.8.3 | None |
| `ydata-profiling` | PyPI | From 3.7.0 to 4.8.3 | None |

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

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

## Is CVE-2024-37062 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-37062 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37062 is a high-severity unsafe deserialization vulnerability in YdataAI ydata-profiling, 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-37062 exists.

Affected packages and fixed versions:
- ydata-profiling (PyPI): affected from 3.7.0 up to 4.8.3; no fix listed
- ydata-profiling (PyPI): affected from 3.7.0 up to 4.8.3; no fix listed
- ydata-profiling (PyPI): affected from 3.7.0 up to 4.8.3; 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-37062/ (Markdown: https://insights.sbomify.com/CVE-2024-37062/index.md)
```

## Sources

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

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