# CVE-2026-68772: ZenML 0.94.6 Remote Code Execution via CloudpickleMaterializer

> Attackers with write access to a shared artifact store can execute arbitrary code by planting malicious pickle files in ZenML.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-p65j-fxc2-99ww

## What is CVE-2026-68772?

CVE-2026-68772 is a high-severity unsafe deserialization vulnerability in ZenML, published on 7 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

ZenML 0.94.6 contains a remote code execution vulnerability in the CloudpickleMaterializer component that allows attackers with write access to a shared artifact store to execute arbitrary code by planting a malicious pickle file. Attackers can replace a stored artifact.pkl file with a crafted cloudpickle payload containing a malicious __reduce__ method, which executes arbitrary system commands when any user or pipeline materializes the artifact through the unsanitized cloudpickle.load() call in cloudpickle_materializer.py.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-68772?


## How do I fix CVE-2026-68772?

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

## Is CVE-2026-68772 being exploited?

There is no known exploitation of CVE-2026-68772 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68772 and fix it if it is affected.

What it is: CVE-2026-68772 is a high-severity unsafe deserialization vulnerability in ZenML, published on 7 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-68772 in the wild and no public exploit code.

Affected product: ZenML. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-68772/ (Markdown: https://insights.sbomify.com/CVE-2026-68772/index.md)
```

## Sources

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

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