# CVE-2026-31235: imgaug RCE (Critical 9.8) ๐Ÿ ๐Ÿ PyPI Not in CISA KEV CRITICAL severity # CVE-2026-31235 โ€” imgaug CRITICAL CVE-2026-31235 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in imgaug. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime. imgaug contains an insecure deserialization vulnerability in BackgroundAugmenter class within multicore.py module Also known asPYSEC-2026-356 Published May 12, 2026 Updated Oct 27, 2026 Affected 1 pkg Patched None yet Exploits None indexed Exploitation data as of Nov 9, 2026 ยท OSV.dev, NVD, FIRST.org (EPSS) ## EPSS Exploitation Probability [via FIRST.org โ†—](https://www.first.org/epss/) 0.5%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs41th percentile โ€” riskier than 41% of all scored CVEsHighest risk 0.00%0.40%0.79%1.19%0.1%0.5%Jun 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 1 pkg affected ๐Ÿ`imgaug` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages โ€” download data is not available via public APIs for these ecosystems. ## Description The imgaug library thru 0.4.0 contains an insecure deserialization vulnerability in its BackgroundAugmenter class within the multicore.py module. The class uses Python's pickle module to deserialize data received via a multiprocessing queue in the \_augment\_images\_worker() method without any safety checks. An attacker who can influence the data placed into this queue (e.g., through social engineering, malicious input scripts, or a compromised shared queue) can provide a malicious pickle payload. When deserialized, this payload can execute arbitrary code in the context of the worker process, leading to remote or local code execution depending on the deployment scenario. ## Affected Packages 1 total Ecosystem Package Vulnerable range Fix ๐ŸPyPI `imgaug` all versions No fix ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for imgaug, including transitive dependencies โ€” a direct dependency you never call can still pull in a vulnerable version. 2. ### Remediation status The records we use list no patched version of imgaug for CVE-2026-31235. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range. 3. ### Mitigate without a patch Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade. ## Frequently Asked Questions The imgaug library thru 0.4.0 contains an insecure deserialization vulnerability in its BackgroundAugmenter class within the multicore.py module. The class uses Python's pickle module to deserialize data received via a multiprocessing queue in the \_augment\_images\_worker() method without any safety checks. An attacker who can influence the data placed into this queue (e.g., through social engineering, malicious input scripts, or a compromised shared queue) can provide a malicious pickle payload. When deserialized, this payload can execute arbitrary code in the context of the worker process, lea O3 Security ยท Impact-Aware SCA ### Is CVE-2026-31235 in your dependencies? Find it across PyPI, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)