# TensorFlow has Segfault in Bincount with XLA

Advisory record · `GHSA-7x4v-9gxg-9hwj`

- **Identifiers:** `GHSA-7x4v-9gxg-9hwj` · `BIT-tensorflow-2023-25675` · `CVE-2023-25675` · `PYSEC-2026-3131` · `PYSEC-2026-3294` · `PYSEC-2026-967`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-697](https://cwe.mitre.org/data/definitions/697.html)
- **Tags:** [CWE-697](https://agentprime.io/advisories/tag/cwe-697.md)
- **Published:** 24 Mar 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Mar 2023, 21:54 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `tensorflow` (PyPI): affected `<2.11.1`; fixed in `2.11.1`
- `tensorflow-cpu` (PyPI): affected `<2.11.1`; fixed in `2.11.1`
- `tensorflow-gpu` (PyPI): affected `<2.11.1`; fixed in `2.11.1`

## Machine-written summary

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

> TensorFlow, tensorflow-cpu and tensorflow-gpu versions before 2.11.1 are affected. When running with XLA, calling tf.raw_ops.Bincount with a weights tensor that is neither the same shape as arr nor empty causes a segfault. The source does not describe what an attacker can do beyond crashing the process. Upgrade to version 2.11.1 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.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0039, the 33rd percentile, on 6 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-7x4v-9gxg-9hwj)

## Sources

- [GitHub Advisory Database: GHSA-7x4v-9gxg-9hwj](https://github.com/advisories/GHSA-7x4v-9gxg-9hwj)
- [OSV: GHSA-7x4v-9gxg-9hwj](https://osv.dev/vulnerability/GHSA-7x4v-9gxg-9hwj)
- <https://github.com/tensorflow/tensorflow/security/advisories/GHSA-7x4v-9gxg-9hwj>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-25675>
- <https://github.com/tensorflow/tensorflow/commit/8ae76cf085f4be26295d2ecf2081e759e04b8acf>
- <https://github.com/tensorflow/tensorflow>

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-7x4v-9gxg-9hwj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7x4v-9gxg-9hwj/>. Everything for agents: <https://agentprime.io/llms.txt>.