How severe is CVE-2024-24590?

CVE-2024-24590 has a CVSS score of 8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-24590?

CVE-2024-24590 affects the following packages: clearml (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2024-24590?

No patched version of clearml has shipped for CVE-2024-24590 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2024-24590 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for clearml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2024-24590 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-24590?

O3 pinpoints whether CVE-2024-24590 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2024-24590 actively exploited in the wild?

Yes. There are 11 known exploit references for CVE-2024-24590, including 7 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is CVE-2024-24590?

CVE-2024-24590 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-24590 published, and has it been updated?

CVE-2024-24590 was published on February 6, 2024 and was last updated on August 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2024-24590

HIGH

CVE-2024-24590 is a high-severity (CVSS 8) Deserialization of Untrusted Data vulnerability in clearml. 11 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2024-24590 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Allegro AI ClearML vulnerable to deserialization of untrusted data

Also known asGHSA-cpcw-9h9m-wqw9PYSEC-2026-1256

Published

Feb 6, 2024

Updated

Aug 8, 2026

Affected

1 pkg

Patched

None yet

Exploits

11 known

Exploitation data as of Aug 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍clearml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Deserialization of untrusted data can occur in versions 0.17.0 to 1.14.2 of the client SDK of Allegro AI’s ClearML platform, enabling a maliciously uploaded artifact to run arbitrary code on an end user’s system when interacted with.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`clearml`	≥ 0.17.0	No fix

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.