# CVE-2026-31235: imgaug contains an insecure deserialization vulnerability in BackgroundAugmenter class within multicore.py module

> An attacker can execute arbitrary code by providing malicious pickle data to the imgaug library's multiprocessing queue.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-g82g-j283-hj97, PYSEC-2026-356

## What is CVE-2026-31235?

CVE-2026-31235 is a critical unsafe deserialization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

3 open source packages ship an affected version, including imgaug.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `imgaug` | PyPI | All versions to 0.4.0 | None |
| `imgaug` | PyPI | All versions to 0.4.0 | None |
| `imgaug` | PyPI | All versions to 0.4.0 | None |

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

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

## Is CVE-2026-31235 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31235 is a critical unsafe deserialization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31235 in the wild and no public exploit code.

Affected packages and fixed versions:
- imgaug (PyPI): affected all versions up to 0.4.0; no fix listed
- imgaug (PyPI): affected all versions up to 0.4.0; no fix listed
- imgaug (PyPI): affected all versions up to 0.4.0; no fix listed

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

## Sources

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

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