How severe is GHSA-cpcw-9h9m-wqw9?

GHSA-cpcw-9h9m-wqw9 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-cpcw-9h9m-wqw9?

GHSA-cpcw-9h9m-wqw9 affects the following packages: clearml (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-cpcw-9h9m-wqw9?

No patched version of clearml has shipped for GHSA-cpcw-9h9m-wqw9 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 GHSA-cpcw-9h9m-wqw9 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for clearml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cpcw-9h9m-wqw9 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 GHSA-cpcw-9h9m-wqw9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cpcw-9h9m-wqw9 can be triaged on real exposure rather than presence alone.

Is GHSA-cpcw-9h9m-wqw9 actively exploited in the wild?

Yes. There are 11 known exploit references for GHSA-cpcw-9h9m-wqw9, 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 is the EPSS score for GHSA-cpcw-9h9m-wqw9?

GHSA-cpcw-9h9m-wqw9 has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-cpcw-9h9m-wqw9?

GHSA-cpcw-9h9m-wqw9 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 GHSA-cpcw-9h9m-wqw9 published, and has it been updated?

GHSA-cpcw-9h9m-wqw9 was published on February 6, 2024 and was last updated on July 7, 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

GHSA-cpcw-9h9m-wqw9 — clearml

HIGH

GHSA-cpcw-9h9m-wqw9 is a high-severity (CVSS 8.8) Deserialization of Untrusted Data vulnerability in clearml. 11 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Allegro AI ClearML vulnerable to deserialization of untrusted data

Also known asCVE-2024-24590PYSEC-2026-1256

Published

Feb 6, 2024

Updated

Jul 7, 2026

Affected

1 pkg

Patched

None yet

Exploits

11 known

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-cpcw-9h9m-wqw9.

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-cpcw-9h9m-wqw9 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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.