imgaug contains an insecure deserialization vulnerability in BackgroundAugmenter class within multicore.py module
CVE-2026-31235GHSA-g82g-j283-hj97
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI imgaug
- Affected
- <= 0.4.0
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-g82g-j283-hj97 lists affected ranges: PyPI imgaug >=0 <=0.4.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-g82g-j283-hj97 lists affected ranges: PyPI imgaug >=0 <=0.4.0
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-31235: 0.47% estimated exploitation activity in the next 30 days; percentile 40.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 5 · amended ·
Amended from osv record GHSA-g82g-j283-hj97
- Revision 4 · amended ·
Amended from ghsa record GHSA-g82g-j283-hj97
- Revision 3 · amended ·
Amended from ghsa record GHSA-g82g-j283-hj97
- Revision 2 · amended ·
Amended from osv record GHSA-g82g-j283-hj97
- Revision 1 · created ·
Published from ghsa record GHSA-g82g-j283-hj97
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-31235 Advisory: imgaug contains an insecure deserialization vulnerability in BackgroundAugmenter class within multicore.py module IDs: CVE-2026-31235, GHSA-g82g-j283-hj97 Record: https://patchnext.com/advisories/cve-2026-31235 (revision 5, source checked 28 Oct 2026, 06:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI imgaug: affected <= 0.4.0 ## Suggested inspection (read-only) - `python -m pip show imgaug`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on imgaug. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-g82g-j283-hj97 (GitHub-reviewed advisory GHSA-g82g-j283-hj97 lists affected ranges: PyPI imgaug >=0 <=0.4.0) - Verified: https://osv.dev/vulnerability/GHSA-g82g-j283-hj97 (OSV record GHSA-g82g-j283-hj97 lists affected ranges: PyPI imgaug >=0 <=0.4.0) Commands are suggestions: review each one before running it.
Loading voting…