Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-m4hf-j54p-p353

Type confusion leading to segfault in Tensorflow

CVSS 6.5 MediumEPSS 0.0085 · 58th percentile

Published by the GitHub Advisory Database at 10 Feb 2022, 00:19 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-m4hf-j54p-p353 · BIT-tensorflow-2022-21731 · CVE-2022-21731 · PYSEC-2022-110 · PYSEC-2022-55 · PYSEC-2026-3211
Weakness (CWE)
CWE-754 · CWE-843
Tags
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.

Affected versions of tensorflow, tensorflow-cpu and tensorflow-gpu are those before 2.5.3, from 2.6.0 before 2.6.3, and from 2.7.0 before 2.7.1. A type confusion in the shape inference for ConcatV2 lets a crafted input bypass a rank check and cause a segfault, enabling denial of service. Upgrade to 2.5.3, 2.6.3, 2.7.1 or later; no workaround is listed.

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.0085, the 58th percentile, on 9 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.