UTC

clearml

4 published advisories; version 2.0.2 or later fixes all but 3 of them.

Registry
PyPI
Advisories
4
Latest fix
2.0.2
Exploited in the wild
None listed
Advisories with no fix yet

3 advisories have no fixed release in any version yet. What can be done meanwhile:

General guidance from ShieldPi, not a vendor fix

  • Path traversal. Limit the folders it can reach at the operating-system level, such as a container or a user with access to only those folders, and keep credentials and keys outside them.GHSA-m95h-p4gg-wfw3
  • Unsafe deserialization. Do not let it load files, models or data from sources you do not trust, and keep its RPC and socket ports reachable only from localhost or hosts you trust.GHSA-cpcw-9h9m-wqw9

Check your projects

shieldpi agent-config checks agent and MCP packages from npm and PyPI, not clearml. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.

osv-scanner scan source -r .

Or check a lockfile against ShieldMap in your browser.

Provenance

Source: github.com/clearml/clearml, named in the package metadata (not verified)

0 of the last 10 releases of clearml were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.

  • 2.2.0
  • 2.1.12
  • 2.1.11
  • 2.1.10
  • 2.1.9
  • 2.1.8
  • 2.1.7
  • 2.1.6
  • 2.1.5
  • 2.1.4

Green: published with provenance. Grey: without.

OpenSSF Scorecard has not scored this repository.

Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.

Advisories
AdvisorySeverityAffectedFixed inPublished
clearml is vulnerable to Path Traversal through its `safe_extract` functionCVE-2025-8917Medium< 2.0.22.0.22025-10-05
Allegro AI ClearML vulnerable to deserialization of untrusted dataCVE-2024-24590High>= 0.17.0, <= 1.14.1No fix yet2024-02-06
Allegro AI ClearML Stores Credentials in Plaintext in MongoDB InstanceCVE-2024-24595Medium<= 1.14.2No fix yet2024-02-06
Allegro AI ClearML path traversal vulnerabilityCVE-2024-24591High>= 0.17.0, <= 1.14.1No fix yet2024-02-06

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].