How severe is CVE-2021-37683?

CVE-2021-37683 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-37683?

CVE-2021-37683 affects the following packages: tensorflow (PyPI), tensorflow (PyPI), tensorflow (PyPI), tensorflow-cpu (PyPI), tensorflow-cpu (PyPI), tensorflow-cpu (PyPI), tensorflow-gpu (PyPI), tensorflow-gpu (PyPI), and 1 more. Ecosystems affected: PyPI.

How do I fix CVE-2021-37683?

Update tensorflow to 2.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-37683 is resolved across your whole dependency graph.

How do I detect CVE-2021-37683 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tensorflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-37683 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2021-37683 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-37683 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-37683?

CVE-2021-37683 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 4th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-37683?

CVE-2021-37683 is classified as CWE-369 (CWE-369). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-37683 published, and has it been updated?

CVE-2021-37683 was published on August 12, 2021 and was last updated on August 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2021-37683 — tensorflow

MEDIUMFix: tensorflow/tensorflow@1e206ba

CVE-2021-37683 is a medium-severity (CVSS 5.5) CWE-369 vulnerability in tensorflow. A fix is available for tensorflow — see the affected versions and patch details below.

FPE in TFLite division operations

Also known asBIT-tensorflow-2021-37683GHSA-rhrq-64mq-hf9hPYSEC-2021-305PYSEC-2021-596PYSEC-2021-794

Published

Aug 12, 2021

Updated

Aug 7, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs4th percentile — riskier than 4% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-37683 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

9 pkgs affected

🐍tensorflow🐍tensorflow🐍tensorflow🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-gpu🐍tensorflow-gpu+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The implementation of division in TFLite is vulnerable to a division by 0 error

There is no check that the divisor tensor does not contain zero elements.

Patches

We have patched the issue in GitHub commit 1e206baedf8bef0334cca3eb92bab134ef525a28.

The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, 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 members of the Aivul Team from Qihoo 360.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`tensorflow`	all versions	2.3.4`pip install --upgrade 'tensorflow==2.3.4'`
🐍PyPI	`tensorflow`	≥ 2.4.0&&< 2.4.3	2.4.3`pip install --upgrade 'tensorflow==2.4.3'`
🐍PyPI	`tensorflow`	≥ 2.5.0&&< 2.5.1	2.5.1`pip install --upgrade 'tensorflow==2.5.1'`
🐍PyPI	`tensorflow-cpu`	all versions	2.3.4`pip install --upgrade 'tensorflow-cpu==2.3.4'`
🐍PyPI	`tensorflow-cpu`	≥ 2.4.0&&< 2.4.3	2.4.3`pip install --upgrade 'tensorflow-cpu==2.4.3'`
🐍PyPI	`tensorflow-cpu`	≥ 2.5.0&&< 2.5.1	2.5.1`pip install --upgrade 'tensorflow-cpu==2.5.1'`

Affected Products

1 product · 6 configurations

Application

tensorflowgoogle

≥ 2.4.0 && < 2.4.3

2 versions

2.5.02.6.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tensorflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tensorflow to 2.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-37683 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact The implementation of division in TFLite is [vulnerable to a division by 0 error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/div.cc) There is no check that the divisor tensor does not contain zero elements. ### Patches We have patched the issue in GitHub commit [1e206baedf8bef0334cca3eb92bab134ef525a28](https://github.com/tensorflow/tensorflow/commit/1e206baedf8bef0334cca3eb92bab134ef525a28). The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, a

O3 Security · Impact-Aware SCA

Is CVE-2021-37683 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.5/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

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

CWE Classification

CWE-369CWE-369

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

tensorflow

7.8/10

Code-Review7/10

Maintained10/10

Dependency-Update-Tool10/10

Branch-ProtectionN/A

Vulnerabilities0/10

Assessed Oct 9, 2026

Timeline

Disclosed

Aug 12, 2021

Last updated

Aug 7, 2026

Identifiers

CVE-2021-37683

GHSA-rhrq-64mq-hf9h

BIT-tensorflow-2021-37683

PYSEC-2021-305

PYSEC-2021-596

References

Advisorygithub.com Advisorynvd.nist.gov Fixgithub.com Webgithub.com Webgithub.com Webgithub.com Webgithub.com Packagegithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting tensorflow are rated as high or higher (top: high).

CVE-2023-33976CVE-2023-25661CVE-2023-25670CVE-2023-25665CVE-2023-27579CVE-2023-25673CVE-2023-25663CVE-2023-25658

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 7, 2026

CVE-2021-37683 — tensorflow

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

For more information

Attribution

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-37683 in your dependencies?