# TensorFlow vulnerable to \`CHECK\` fail in \`CollectiveGather\`

Advisory record · `GHSA-fhfc-2q7x-929f`

- **Identifiers:** `GHSA-fhfc-2q7x-929f` · `BIT-tensorflow-2022-35994` · `CVE-2022-35994` · `PYSEC-2026-3172` · `PYSEC-2026-3320` · `PYSEC-2026-990`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-617](https://cwe.mitre.org/data/definitions/617.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 16 Sept 2022
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 16 Sept 2022, 22:11 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `tensorflow` (PyPI): affected `<2.7.2 || >=2.8.0, <2.8.1 || >=2.9.0, <2.9.1`; fixed in `2.7.2`, `2.8.1`, `2.9.1`
- `tensorflow-cpu` (PyPI): affected `<2.7.2 || >=2.8.0, <2.8.1 || >=2.9.0, <2.9.1`; fixed in `2.7.2`, `2.8.1`, `2.9.1`
- `tensorflow-gpu` (PyPI): affected `<2.7.2 || >=2.8.0, <2.8.1 || >=2.9.0, <2.9.1`; fixed in `2.7.2`, `2.8.1`, `2.9.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> TensorFlow (packages tensorflow, tensorflow-cpu and tensorflow-gpu) versions before 2.7.2, from 2.8.0 before 2.8.1, and from 2.9.0 before 2.9.1 are affected. When CollectiveGather receives a scalar input, a CHECK failure occurs, which can be used to cause a denial of service. Upgrade to 2.7.2, 2.8.1, 2.9.1 or later. The source gives few details about the attack conditions.

Written 6 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

- 5.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0049, the 42nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:01 UTC: First seen by agentprime
- 31 Oct 2026, 15:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-fhfc-2q7x-929f)

## Sources

- [GitHub Advisory Database: GHSA-fhfc-2q7x-929f](https://github.com/advisories/GHSA-fhfc-2q7x-929f)
- [OSV: GHSA-fhfc-2q7x-929f](https://osv.dev/vulnerability/GHSA-fhfc-2q7x-929f)
- <https://github.com/tensorflow/tensorflow/security/advisories/GHSA-fhfc-2q7x-929f>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-35994>
- <https://github.com/tensorflow/tensorflow/commit/c1f491817dec39a26be3c574e86a88c30f3c4770>
- <https://github.com/tensorflow/tensorflow>
- <https://github.com/tensorflow/tensorflow/releases/tag/v2.10.0>

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 (<https://api.agentprime.io/mcp>), 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: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-fhfc-2q7x-929f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fhfc-2q7x-929f/>. Everything for agents: <https://agentprime.io/llms.txt>.
