# Interpreter crash from \`tf.io.decode_raw\` Advisory record · `GHSA-8pmx-p244-g88h` - **Identifiers:** `GHSA-8pmx-p244-g88h` · `BIT-tensorflow-2021-29614` · `CVE-2021-29614` · `PYSEC-2021-251` · `PYSEC-2021-542` · `PYSEC-2021-740` - **State:** Confirmed - **Severity:** CVSS 7.1 High - **Critical:** No - **Weakness (CWE):** [CWE-665](https://cwe.mitre.org/data/definitions/665.html) · [CWE-787](https://cwe.mitre.org/data/definitions/787.html) - **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md) · [CWE-665](https://agentprime.io/advisories/tag/cwe-665.md) - **Published:** 21 May 2021 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 21 May 2021, 14:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `tensorflow` (PyPI): affected `<2.1.4 || >=2.2.0, <2.2.3 || >=2.3.0, <2.3.3 || >=2.4.0, <2.4.2`; fixed in `2.1.4`, `2.2.3`, `2.3.3`, `2.4.2` - `tensorflow-cpu` (PyPI): affected `<2.1.4 || >=2.2.0, <2.2.3 || >=2.3.0, <2.3.3 || >=2.4.0, <2.4.2`; fixed in `2.1.4`, `2.2.3`, `2.3.3`, `2.4.2` - `tensorflow-gpu` (PyPI): affected `<2.1.4 || >=2.2.0, <2.2.3 || >=2.3.0, <2.3.3 || >=2.4.0, <2.4.2`; fixed in `2.1.4`, `2.2.3`, `2.3.3`, `2.4.2` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Affected versions of tensorflow, tensorflow-cpu and tensorflow-gpu are those before 2.1.4, from 2.2.0 before 2.2.3, from 2.3.0 before 2.3.3, and from 2.4.0 before 2.4.2. Calling tf.io.decode_raw with fixed_length and a wider datatype writes past the bounds of the output buffer, which can crash the Python interpreter; the source notes more severe attacks may be possible. Upgrade to 2.1.4, 2.2.3, 2.3.3, 2.4.2 or later. Written 5 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 7.1 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0022, the 12th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:37 UTC: First seen by agentprime - 31 Oct 2026, 14:37 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8pmx-p244-g88h) ## Sources - [GitHub Advisory Database: GHSA-8pmx-p244-g88h](https://github.com/advisories/GHSA-8pmx-p244-g88h) - [OSV: GHSA-8pmx-p244-g88h](https://osv.dev/vulnerability/GHSA-8pmx-p244-g88h) - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .