Skip to main content
VulnerabilityPublished

CVE-2026-68772: ZenML 0.94.6 contains a remote code execution vulnerability in the CloudpickleMaterializer component that allows attackers with write access to a

Affects zenmlSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.0 High.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
PyPIzenmlpkg:pypi/zenmlOther threatsAffected
  • =0.94.6
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict write access to the shared artifact store to trusted users only. Avoid materializing artifacts from untrusted or unverified sources. Monitor vendor channels for updates or official patches addressing this vulnerability.

Description

ZenML version 0.94.6 contains a remote code execution vulnerability in its CloudpickleMaterializer component. This flaw allows attackers with write access to a shared artifact store to execute arbitrary code by replacing a stored artifact.pkl file with a malicious cloudpickle payload. The vulnerability arises from the unsanitized use of cloudpickle.load(), which executes the malicious __reduce__ method embedded in the payload during artifact materialization.

References

Community reviews

Loading reviews…