Advisory record · GHSA-gcvh-66ff-4mwm

`CHECK`-failures in Tensorflow

CVSS 6.5 MediumEPSS 0.0079 · 57th percentile

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

PackageEcosystemAffectedFixed in
tensorflowPyPI<2.5.3 || >=2.6.0, <2.6.3 || >=2.7.0, <2.7.12.5.3, 2.6.3, 2.7.1
tensorflow-cpuPyPI<2.5.3 || >=2.6.0, <2.6.3 || >=2.7.0, <2.7.12.5.3, 2.6.3, 2.7.1
tensorflow-gpuPyPI<2.5.3 || >=2.6.0, <2.6.3 || >=2.7.0, <2.7.12.5.3, 2.6.3, 2.7.1
Identifiers
GHSA-gcvh-66ff-4mwm · BIT-tensorflow-2022-21734 · CVE-2022-21734 · PYSEC-2022-113 · PYSEC-2022-58 · PYSEC-2026-3187
Weakness (CWE)
CWE-617 · CWE-843
Published
10 Feb 2022
Updated
10 Sept 2026

Machine-written summary

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

TensorFlow (tensorflow, tensorflow-cpu and tensorflow-gpu packages) versions before 2.5.3, from 2.6.0 before 2.6.3, and from 2.7.0 before 2.7.1 are vulnerable. The MapStage operation crashes on a CHECK failure when the key tensor is not a scalar, which an attacker could trigger by supplying such input to the operation. Upgrade to 2.5.3, 2.6.3, 2.7.1 or later. The source gives few details on the exact conditions under which the crash can be triggered.

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

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

Timeline

  1. 31 Oct 2026, 14:37 UTC First seen by agentprime
  2. 31 Oct 2026, 14:37 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.