Advisory record · GHSA-jq6x-99hj-q636

Seg fault in `ndarray_tensor_bridge` due to zero and large inputs

CVSS 4.8 MediumEPSS 0.0037 · 31st percentile

Published by the GitHub Advisory Database at 21 Nov 2022, 20:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
tensorflowPyPI<2.8.4 || >=2.9.0, <2.9.3 || >=2.10.0, <2.10.12.8.4, 2.9.3, 2.10.1
tensorflow-cpuPyPI<2.8.4 || >=2.9.0, <2.9.3 || >=2.10.0, <2.10.12.8.4, 2.9.3, 2.10.1
tensorflow-gpuPyPI<2.8.4 || >=2.9.0, <2.9.3 || >=2.10.0, <2.10.12.8.4, 2.9.3, 2.10.1
Identifiers
GHSA-jq6x-99hj-q636 · BIT-tensorflow-2022-41884 · CVE-2022-41884 · PYSEC-2026-1013 · PYSEC-2026-3208 · PYSEC-2026-3345
Weakness (CWE)
CWE-670
Published
21 Nov 2022
Updated
13 Jul 2026

Machine-written summary

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

Seg fault in tensorflow, tensorflow-cpu and tensorflow-gpu versions before 2.8.4, from 2.9.0 before 2.9.3, and from 2.10.0 before 2.10.1 can be triggered by creating a numpy array with a shape that contains a zero dimension and other dimensions whose product is very large. The source does not describe the attacker's required access. Upgrade to tensorflow 2.8.4, 2.9.3, 2.10.1 or later, or to tensorflow-cpu or tensorflow-gpu at the same versions.

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

ScoreRatingCVSSVectorSource
4.8 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0037, the 31st percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:01 UTC First seen by agentprime
  2. 31 Oct 2026, 15:01 UTC Confirmed by OSV

Sources

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.