CVE-2021-29550

LOWNVD 2.52.5—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). 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
2.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 2.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a runtime division by zero error and denial of service in tf.raw_ops.FractionalAvgPool. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L85-L89) computes a divisor quantity by dividing two user controlled values. The user controls the values of input_size[i] and pooling_ratio_[i] (via the value.shape() and pooling_ratio arguments). If the value in input_size[i] is smaller than the pooling_ratio_[i], then the floor operation results in output_size[i] being 0. The DCHECK_GT line is a no-op outside of debug mode, so in released versions of TF this does not trigger. Later, these computed values are used as arguments(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L96-L99) to GeneratePoolingSequence(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_pool_common.cc#L100-L108). There, the first computation is a division in a modulo operation. Since output_length can be 0, this results in runtime crashing. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.

CVSS v3
2.5
EG Score
2.5LOWmedium confidence
EG Risk
16
EG Risk 16/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity25% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

May 14, 2021

Last Modified

November 21, 2024

References (4)

Affected Packages

(3 across 1 ecosystem)
PyPI(3)
PackageVulnerable rangeFix by version rangeDependents
tensorflow0.12.0 ... 2.4.2 (102 versions)
  • every version up to 2.1.4: fixed in 2.1.4
  • 2.2.0 up to 2.2.3: fixed in 2.2.3
  • 2.3.0 up to 2.3.3: fixed in 2.3.3
  • 2.4.0 up to 2.4.2: fixed in 2.4.2
  • every version up to 2.2.0rc0: fixed in 2.2.0rc0
  • 2.2.0 up to 2.3.0rc0: fixed in 2.3.0rc0
  • 2.3.0 up to 2.3.4: fixed in 2.3.4
  • 2.4.0 up to 2.4.3: fixed in 2.4.3
—
tensorflow-cpu1.15.0 ... 2.4.2 (17 versions)
  • every version up to 2.1.4: fixed in 2.1.4
  • 2.2.0 up to 2.2.3: fixed in 2.2.3
  • 2.3.0 up to 2.3.3: fixed in 2.3.3
  • 2.4.0 up to 2.4.2: fixed in 2.4.2
  • every version up to 2.2.0rc0: fixed in 2.2.0rc0
  • 2.2.0 up to 2.3.0rc0: fixed in 2.3.0rc0
  • 2.3.0 up to 2.3.4: fixed in 2.3.4
  • 2.4.0 up to 2.4.3: fixed in 2.4.3
—
tensorflow-gpu0.12.0 ... 2.4.2 (52 versions)
  • every version up to 2.1.4: fixed in 2.1.4
  • 2.2.0 up to 2.2.3: fixed in 2.2.3
  • 2.3.0 up to 2.3.3: fixed in 2.3.3
  • 2.4.0 up to 2.4.2: fixed in 2.4.2
  • every version up to 2.2.0rc0: fixed in 2.2.0rc0
  • 2.2.0 up to 2.3.0rc0: fixed in 2.3.0rc0
  • 2.3.0 up to 2.3.4: fixed in 2.3.4
  • 2.4.0 up to 2.4.3: fixed in 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 / 32× 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.

Showing the most recent 100 of 177 total refreshes for this CVE.

  1. 2026-10-09 20:04 UTCEPSS rescore
  2. 2026-10-08 16:39 UTCEPSS rescore
  3. 2026-10-07 23:44 UTCEPSS rescore
  4. 2026-10-06 15:14 UTCEPSS rescore
  5. 2026-10-05 17:40 UTCEPSS rescore
  6. 2026-10-04 23:19 UTCEPSS rescore
  7. 2026-10-03 14:22 UTCEPSS rescore
  8. 2026-10-03 14:22 UTCEPSS rescore
  9. 2026-10-02 16:22 UTCEPSS rescore
  10. 2026-10-01 19:46 UTCEPSS rescore
  11. 2026-09-30 15:34 UTCEG score recompute
  12. 2026-09-30 15:00 UTCEPSS rescore
  13. 2026-09-29 15:15 UTCEPSS rescore
  14. 2026-09-28 13:47 UTCEPSS rescore
  15. 2026-09-26 15:54 UTCEPSS rescore
  16. 2026-09-26 15:54 UTCEPSS rescore
  17. 2026-09-26 02:12 UTCOSV refresh
  18. 2026-09-26 00:21 UTCEPSS rescore
  19. 2026-09-24 14:00 UTCEPSS rescore
  20. 2026-09-23 13:44 UTCEPSS rescore
  21. 2026-09-21 20:28 UTCEPSS rescore
  22. 2026-09-19 15:37 UTCEPSS rescore
  23. 2026-09-18 19:23 UTCEPSS rescore
  24. 2026-09-17 19:23 UTCEPSS rescore
  25. 2026-09-17 19:23 UTCEPSS rescore
Show 75 more
  1. 2026-09-16 14:05 UTCEPSS rescore
  2. 2026-09-15 03:06 UTCEPSS rescore
  3. 2026-09-15 03:06 UTCEPSS rescore
  4. 2026-09-13 16:43 UTCEPSS rescore
  5. 2026-09-12 14:57 UTCEPSS rescore
  6. 2026-09-11 14:49 UTCEPSS rescore
  7. 2026-09-11 09:33 UTCEPSS rescore
  8. 2026-09-08 21:56 UTCEPSS rescore
  9. 2026-09-07 15:58 UTCEPSS rescore
  10. 2026-09-06 17:01 UTCOSV refresh
  11. 2026-09-06 13:44 UTCEPSS rescore
  12. 2026-09-05 15:25 UTCEPSS rescore
  13. 2026-09-04 13:57 UTCEPSS rescore
  14. 2026-09-04 05:03 UTCEPSS rescore
  15. 2026-09-04 05:03 UTCEPSS rescore
  16. 2026-09-02 14:08 UTCEPSS rescore
  17. 2026-09-01 13:50 UTCEPSS rescore
  18. 2026-09-01 03:32 UTCEPSS rescore
  19. 2026-08-30 19:14 UTCEPSS rescore
  20. 2026-08-28 21:37 UTCEPSS rescore
  21. 2026-08-27 14:22 UTCEPSS rescore
  22. 2026-08-26 14:42 UTCEPSS rescore
  23. 2026-08-25 13:45 UTCEPSS rescore
  24. 2026-08-24 14:12 UTCEPSS rescore
  25. 2026-08-23 00:16 UTCEPSS rescore
  26. 2026-08-21 23:46 UTCEPSS rescore
  27. 2026-08-20 22:52 UTCEPSS rescore
  28. 2026-08-20 03:04 UTCOSV refresh
  29. 2026-08-19 17:01 UTCEPSS rescore
  30. 2026-08-18 13:45 UTCEPSS rescore
  31. 2026-08-17 13:44 UTCEPSS rescore
  32. 2026-08-16 14:53 UTCEPSS rescore
  33. 2026-08-16 02:11 UTCEPSS rescore
  34. 2026-08-16 02:11 UTCEPSS rescore
  35. 2026-08-15 01:27 UTCEPSS rescore
  36. 2026-08-13 21:57 UTCEPSS rescore
  37. 2026-08-12 13:47 UTCEPSS rescore
  38. 2026-08-11 13:38 UTCEPSS rescore
  39. 2026-08-09 13:43 UTCEPSS rescore
  40. 2026-08-08 16:33 UTCEPSS rescore
  41. 2026-08-07 16:23 UTCEPSS rescore
  42. 2026-08-06 13:43 UTCEPSS rescore
  43. 2026-08-05 19:14 UTCEPSS rescore
  44. 2026-08-04 21:57 UTCOSV refresh
  45. 2026-08-04 15:06 UTCEPSS rescore
  46. 2026-08-04 10:34 UTCEPSS rescore
  47. 2026-08-03 10:33 UTCEPSS rescore
  48. 2026-08-02 02:24 UTCEPSS rescore
  49. 2026-08-01 04:13 UTCEPSS rescore
  50. 2026-07-30 16:25 UTCEPSS rescore
  51. 2026-07-30 16:25 UTCEPSS rescore
  52. 2026-07-30 01:28 UTCEPSS rescore
  53. 2026-07-30 01:27 UTCEPSS rescore
  54. 2026-07-28 15:33 UTCEPSS rescore
  55. 2026-07-26 14:52 UTCEPSS rescore
  56. 2026-07-26 14:52 UTCEPSS rescore
  57. 2026-07-25 14:15 UTCEPSS rescore
  58. 2026-07-24 14:15 UTCEPSS rescore
  59. 2026-07-23 14:16 UTCEPSS rescore
  60. 2026-07-23 01:59 UTCEG score recompute
  61. 2026-07-22 22:46 UTCEG score recompute
  62. 2026-07-22 14:06 UTCEPSS rescore
  63. 2026-07-22 14:06 UTCEPSS rescore
  64. 2026-07-21 15:22 UTCEPSS rescore
  65. 2026-07-21 15:22 UTCEPSS rescore
  66. 2026-07-20 17:05 UTCEPSS rescore
  67. 2026-07-19 14:28 UTCEPSS rescore
  68. 2026-07-19 02:27 UTCEPSS rescore
  69. 2026-07-19 02:27 UTCEPSS rescore
  70. 2026-07-18 20:29 UTCOSV refresh
  71. 2026-07-18 10:02 UTCEPSS rescore
  72. 2026-07-18 10:02 UTCEPSS rescore
  73. 2026-07-16 17:00 UTCEPSS rescore
  74. 2026-07-15 16:55 UTCEPSS rescore
  75. 2026-07-15 16:55 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2021-29550?
CVE-2021-29550 is a low vulnerability published on May 14, 2021. TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a runtime division by zero error and denial of service in tf.rawops.FractionalAvgPool. This is because the…
When was CVE-2021-29550 disclosed?
CVE-2021-29550 was first published on May 14, 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-29550 actively exploited?
CVE-2021-29550 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-29550?
CVE-2021-29550 has a CVSS v3 base score of 2.5 (NVD).
How do I remediate CVE-2021-29550?
A fix for CVE-2021-29550 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2021-29550?

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

Book a Demo →Browse All CVEs