Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-rww7-2gpw-fv6j

Crash when type cannot be specialized in Tensorflow

CVSS 6.5 MediumEPSS 0.010 · 63rd percentile

Published by the GitHub Advisory Database at 9 Feb 2022, 23:28 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-rww7-2gpw-fv6j · BIT-tensorflow-2022-23572 · CVE-2022-23572 · PYSEC-2022-136 · PYSEC-2022-81 · PYSEC-2026-3241
Weakness (CWE)
CWE-617 · CWE-754
Tags
Published
9 Feb 2022
Updated
13 Jul 2026

Machine-written summary

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

TensorFlow versions before 2.5.3, from 2.6.0 before 2.6.3, and from 2.7.0 before 2.7.1 (also tensorflow-cpu and tensorflow-gpu) can crash when shape inference fails to specialize a type. The source describes this as a crash rather than a broader compromise, and it gives few details on how an attacker would trigger it. Upgrade to 2.5.3, 2.6.3, 2.7.1 or later.

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
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.010, the 63rd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

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