Quick answers
- Is CVE-2026-100845 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100845 being exploited in the wild.
- How severe is CVE-2026-100845?
- High severity, with a CVSS score of 7.8, published 27 September 2026.
- Which products and versions are affected?
- Project-MONAI MONAI before 1.6.0; monai (PyPI) ECOSYSTEM:introduced=0,fixed=1.6.0.
- Is there a fix for CVE-2026-100845?
- Yes. monai (PyPI): upgrade to 1.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100845 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-100845?
- Check whether you run Project-MONAI MONAI or monai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- monai (PyPI): upgrade to 1.6.0 or later
pip install "monai>=1.6.0"
Technical details
The NumpyReader class unconditionally calls numpy.load() with allow_pickle=True when reading .npy and .npz files, enabling arbitrary code execution via pickle deserialization. The vulnerability affects the entire MONAI data pipeline (LoadImage, PersistentDataset, CacheDataset, SmartCacheDataset) and the allow_pickle parameter is hardcoded and cannot be overridden by users. An attacker with the ability to control input .npy files can execute arbitrary code with the privileges of the MONAI process.
Affected products
- Project-MONAI MONAI before 1.6.0
Identifiers
- CVE-2026-100845
- GHSA-wg9g-w2j2-8pgr
- PYSEC-2026-4020
Timeline
- 2026-06-11: disclosed
- 2026-09-26: advisory
- 2026-09-27: patched: Version 1.6.0 released