---
id: CVE-2022-23571
aliases:
  - GHSA-j3mj-fhpq-qqjj
  - BIT-tensorflow-2022-23571
  - PYSEC-2022-135
  - PYSEC-2022-80
  - PYSEC-2026-3204
title: Reachable Assertion in Tensorflow
summary: Reachable Assertion in Tensorflow
severity: medium
cvss: 6.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
vendor: tensorflow
product: tensorflow
ecosystem: pip
affected:
  - tensorflow < 2.5.3
  - 'tensorflow >= 2.6.0, < 2.6.3'
  - 'tensorflow >= 2.7.0, < 2.7.1'
  - tensorflow-cpu < 2.5.3
  - 'tensorflow-cpu >= 2.6.0, < 2.6.3'
  - 'tensorflow-cpu >= 2.7.0, < 2.7.1'
  - tensorflow-gpu < 2.5.3
  - 'tensorflow-gpu >= 2.6.0, < 2.6.3'
  - 'tensorflow-gpu >= 2.7.0, < 2.7.1'
patched:
  - tensorflow 2.5.3
  - tensorflow 2.6.3
  - tensorflow 2.7.1
  - tensorflow-cpu 2.5.3
  - tensorflow-cpu 2.6.3
  - tensorflow-cpu 2.7.1
  - tensorflow-gpu 2.5.3
  - tensorflow-gpu 2.6.3
  - tensorflow-gpu 2.7.1
published: '2022-02-09'
updated: '2026-07-13'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-j3mj-fhpq-qqjj'
references:
  - url: >-
      https://github.com/tensorflow/tensorflow/security/advisories/GHSA-j3mj-fhpq-qqjj
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2022-23571'
  - url: >-
      https://github.com/tensorflow/tensorflow/commit/5b491cd5e41ad63735161cec9c2a568172c8b6a3
  - url: >-
      https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2022-80.yaml
  - url: >-
      https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2022-135.yaml
  - url: 'https://github.com/tensorflow/tensorflow'
tags:
  - osv
  - pip
epss: 0.00473
epssPercentile: 0.40118
ingestedAt: '2026-07-13T18:57:59.596Z'
---

## Overview

### Impact
When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments, if the tensors have an invalid `dtype` and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes.

### Patches
We have patched the issue in GitHub commit [5b491cd5e41ad63735161cec9c2a568172c8b6a3](https://github.com/tensorflow/tensorflow/commit/5b491cd5e41ad63735161cec9c2a568172c8b6a3).
  
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. 
  
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.

## Affected packages

- `tensorflow < 2.5.3`
- `tensorflow >= 2.6.0, < 2.6.3`
- `tensorflow >= 2.7.0, < 2.7.1`
- `tensorflow-cpu < 2.5.3`
- `tensorflow-cpu >= 2.6.0, < 2.6.3`
- `tensorflow-cpu >= 2.7.0, < 2.7.1`
- `tensorflow-gpu < 2.5.3`
- `tensorflow-gpu >= 2.6.0, < 2.6.3`
- `tensorflow-gpu >= 2.7.0, < 2.7.1`

## Remediation

Upgrade to a patched release:

- `tensorflow 2.5.3`
- `tensorflow 2.6.3`
- `tensorflow 2.7.1`
- `tensorflow-cpu 2.5.3`
- `tensorflow-cpu 2.6.3`
- `tensorflow-cpu 2.7.1`
- `tensorflow-gpu 2.5.3`
- `tensorflow-gpu 2.6.3`
- `tensorflow-gpu 2.7.1`