CVE-2022-21729Medium· 6.5▾ Sunlit

Overflow and uncaught divide by zero in Tensorflow

▾ Sunlit zone — Low / medium · no exploitation signal

Depth score36/ 100 · Low

impact 35.8 · likelihood 0.2 · exploitation 0

⚡ Agent-ready:Raw markdown ↗JSON ↗

Proof of concept

Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.

…

Published

Feb 10, 2022

Updated

Sep 10, 2026

CVSS

6.5

Vendor

tensorflow

Product

tensorflow

CWE

—

Depth score

36 · Low

EPSS

0.79% · p54

Platforms

—

Source

OSV

Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS history

Exploit-prediction probability, daily snapshots since Jul 13.

0.8% → 0.8%

Timeline

Disclosure to exploitation, from the record and what we observed since indexing it.

4 events · 1673 days

Feb 10, 2022Published
Disclosed via OSV
Jul 13, 2026EPSS first tracked
0.8%
Sep 6, 2026EPSS peak
0.8% → 0.8%
Sep 10, 2026Record revised
Last analysed / modified upstream

tensorflow #osv #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 in

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

Full technical detail▾

Overview

Impact

The implementation of UnravelIndex is vulnerable to a division by zero caused by an integer overflow bug:

import tensorflow as tf

tf.raw_ops.UnravelIndex(indices=-0x100000,dims=[0x100000,0x100000])

Patches

We have patched the issue in GitHub commit 58b34c6c8250983948b5a781b426f6aa01fd47af.

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 for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by Yu Tian of Qihoo 360 AIVul Team.

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

References

Related vulnerabilities

Connected by shared product, vendor, weakness, or advisory.

#osv#pip

← Back to feed

CVE-2022-21729Medium· 6.5▾ Sunlit

Overflow and uncaught divide by zero in Tensorflow

▾ Sunlit zone — Low / medium · no exploitation signal

Depth score36/ 100 · Low

impact 35.8 · likelihood 0.2 · exploitation 0

⚡ Agent-ready:Raw markdown ↗JSON ↗

Proof of concept

Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.

…

Published

Feb 10, 2022

Updated

Sep 10, 2026

CVSS

6.5

Vendor

tensorflow

Product

tensorflow

CWE

—

Depth score

36 · Low

EPSS

0.79% · p54

Platforms

—

Source

OSV

Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS history

Exploit-prediction probability, daily snapshots since Jul 13.

0.8% → 0.8%

Timeline

Disclosure to exploitation, from the record and what we observed since indexing it.

4 events · 1673 days

Feb 10, 2022Published
Disclosed via OSV
Jul 13, 2026EPSS first tracked
0.8%
Sep 6, 2026EPSS peak
0.8% → 0.8%
Sep 10, 2026Record revised
Last analysed / modified upstream

tensorflow #osv #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 in

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

Full technical detail▾

Overview

Impact

The implementation of UnravelIndex is vulnerable to a division by zero caused by an integer overflow bug:

import tensorflow as tf

tf.raw_ops.UnravelIndex(indices=-0x100000,dims=[0x100000,0x100000])

Patches

We have patched the issue in GitHub commit 58b34c6c8250983948b5a781b426f6aa01fd47af.

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 for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by Yu Tian of Qihoo 360 AIVul Team.

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

References

Related vulnerabilities

Connected by shared product, vendor, weakness, or advisory.

#osv#pip