Vulnerability · Published Sep 27, 2026 · Assigned by VulnCheck

CVE-2026-100841MONAI through 1.6.0 PersistentDataset Remote Code Execution via Pickle Cache

High 7.8

In plain English

A high-severity unsafe deserialization in MONAI from Project-MONAI. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities).

Severity (CVSS 3.1)7.8High

Exploit odds (30 days)0.1%top 97.5% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official description

In MONAI 1.6.0, PersistentDataset (monai/data/dataset.py) explicitly rejects the combination track_meta=True with weights_only=True, forcing users who cache MetaTensors (the default tensor type in MONAI >= 1.0) to run torch.load(hashfile, weights_only=False). Related cache helpers in monai/data/utils.py also call pickle.loads on cached content and derive cache keys with hashlib.md5. As a result, a local user with write access to a shared or world-writable cache_dir (e.g. /tmp/monai_cache, HPC scratch, ~/.cache/monai) can place a malicious pickle file that is deserialized the next time another user's MONAI pipeline reads the cache, resulting in arbitrary code execution in that user's context. All released versions of the monai pip package are affected; no patched version is available as of the advisory.

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
PyPI	monai	no fix listed	PYSEC-2026-4016

Affected products (as reported)

Vendor	Product	Versions
Project-MONAI	MONAI	0 – through 1.6.0

Weakness: CWE-502 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

GitHub Security Advisory (GHSA-636w-j999-g7x5) vendor-advisory
VulnCheck Advisory: MONAI 1.6.0 PersistentDataset Remote Code Execution via Pickle Cache third-party-advisory