CVE-2021-37645

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of tf.raw_ops.QuantizeAndDequantizeV4Grad is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The implementation uses the axis value as the size argument to absl::InlinedVector constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer. We have patched the issue in GitHub commit 96f364a1ca3009f98980021c4b32be5fdcca33a1. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, and TensorFlow 2.4.3, as these are also affected and still in supported range.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
4.8%
KEV
Not listed

Published

August 12, 2021

Last Modified

November 21, 2024

References (4)

Affected Packages

(3 across 1 ecosystem)
PyPI(3)
PackageVulnerable rangeFixed inDependents
tensorflow2.3.0 ... 2.4.2 (7 versions)2.4.3—
tensorflow-cpu2.3.0 ... 2.4.2 (7 versions)2.4.3—
tensorflow-gpu2.3.0 ... 2.4.2 (7 versions)2.4.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-11 08:25 UTCEPSS rescore
  3. 2026-07-09 19:07 UTCEPSS rescore
  4. 2026-07-08 15:12 UTCEPSS rescore
  5. 2026-07-07 13:43 UTCEPSS rescore
  6. 2026-07-06 16:25 UTCEPSS rescore
  7. 2026-07-05 02:28 UTCEPSS rescore
  8. 2026-07-05 02:28 UTCEPSS rescore
  9. 2026-07-04 06:29 UTCEPSS rescore
  10. 2026-07-04 06:29 UTCEPSS rescore
  11. 2026-07-01 15:04 UTCEPSS rescore
  12. 2026-06-30 23:20 UTCEPSS rescore
  13. 2026-06-30 23:20 UTCEPSS rescore
  14. 2026-06-30 19:00 UTCOSV refresh
  15. 2026-06-29 14:04 UTCEPSS rescore
  16. 2026-06-28 14:05 UTCEPSS rescore
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-28 04:54 UTCEPSS rescore
  19. 2026-06-27 03:06 UTCEPSS rescore
  20. 2026-06-25 13:48 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-24 14:03 UTCEPSS rescore
  23. 2026-06-24 14:03 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
Show 46 more
  1. 2026-06-22 14:24 UTCEPSS rescore
  2. 2026-06-22 14:24 UTCEPSS rescore
  3. 2026-06-21 14:55 UTCEPSS rescore
  4. 2026-06-21 01:58 UTCEPSS rescore
  5. 2026-06-21 01:58 UTCEPSS rescore
  6. 2026-06-19 19:24 UTCEPSS rescore
  7. 2026-06-19 19:24 UTCEPSS rescore
  8. 2026-06-18 17:51 UTCEPSS rescore
  9. 2026-06-18 17:51 UTCEPSS rescore
  10. 2026-06-17 17:51 UTCEPSS rescore
  11. 2026-06-16 17:51 UTCEPSS rescore
  12. 2026-06-16 17:51 UTCEPSS rescore
  13. 2026-06-15 17:46 UTCEPSS rescore
  14. 2026-06-14 23:15 UTCEPSS rescore
  15. 2026-06-13 22:58 UTCEPSS rescore
  16. 2026-06-13 22:58 UTCEPSS rescore
  17. 2026-06-13 00:14 UTCOSV refresh
  18. 2026-06-12 23:10 UTCEPSS rescore
  19. 2026-06-12 23:10 UTCEPSS rescore
  20. 2026-06-11 13:58 UTCEPSS rescore
  21. 2026-06-10 22:16 UTCEPSS rescore
  22. 2026-06-10 13:20 UTCEPSS rescore
  23. 2026-06-08 14:15 UTCEPSS rescore
  24. 2026-06-08 14:15 UTCEPSS rescore
  25. 2026-06-06 13:46 UTCEPSS rescore
  26. 2026-06-06 13:46 UTCEPSS rescore
  27. 2026-06-06 13:46 UTCEPSS rescore
  28. 2026-06-05 22:45 UTCEPSS rescore
  29. 2026-06-04 13:10 UTCEPSS rescore
  30. 2026-06-04 13:10 UTCEPSS rescore
  31. 2026-06-01 13:50 UTCEPSS rescore
  32. 2026-06-01 13:50 UTCEPSS rescore
  33. 2026-05-31 22:29 UTCEPSS rescore
  34. 2026-05-31 22:29 UTCEPSS rescore
  35. 2026-05-29 13:42 UTCEPSS rescore
  36. 2026-05-29 13:42 UTCEPSS rescore
  37. 2026-05-28 13:43 UTCEPSS rescore
  38. 2026-05-28 13:43 UTCEPSS rescore
  39. 2026-05-27 13:39 UTCEPSS rescore
  40. 2026-05-27 13:39 UTCEPSS rescore
  41. 2026-05-27 13:39 UTCEPSS rescore
  42. 2026-05-26 13:42 UTCEPSS rescore
  43. 2026-05-26 12:07 UTCEG score recompute
  44. 2026-05-26 07:17 UTCEPSS rescore
  45. 2026-05-26 07:17 UTCEPSS rescore
  46. 2026-05-26 07:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2021-37645?
CVE-2021-37645 is a medium vulnerability published on August 12, 2021. TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of tf.rawops.QuantizeAndDequantizeV4Grad is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this…
When was CVE-2021-37645 disclosed?
CVE-2021-37645 was first published in the National Vulnerability Database on August 12, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-37645 actively exploited?
CVE-2021-37645 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2021-37645?
CVE-2021-37645 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2021-37645?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-37645, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-37645

Explore →

Is Your Infrastructure Affected by CVE-2021-37645?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs