CVE-2021-29530

LOWNVD 2.52.5—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 86% 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
Trending — 3 sources updated this week
2.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 2.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. An attacker can trigger a null pointer dereference by providing an invalid permutation to tf.raw_ops.SparseMatrixSparseCholesky. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/080f1d9e257589f78b3ffb75debf584168aa6062/tensorflow/core/kernels/sparse/sparse_cholesky_op.cc#L85-L86) fails to properly validate the input arguments. Although ValidateInputs is called and there are checks in the body of this function, the code proceeds to the next line in ValidateInputs since OP_REQUIRES(https://github.com/tensorflow/tensorflow/blob/080f1d9e257589f78b3ffb75debf584168aa6062/tensorflow/core/framework/op_requires.h#L41-L48) is a macro that only exits the current function. Thus, the first validation condition that fails in ValidateInputs will cause an early return from that function. However, the caller will continue execution from the next line. The fix is to either explicitly check context->status() or to convert ValidateInputs to return a Status. 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.5(medium)
EG Risk
16(Track)
EG Risk 16/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS
14.2%
KEV
Not listed

Published

May 14, 2021

Last Modified

November 21, 2024

References (4)

Affected Packages

(3 across 1 ecosystem)
PyPI(3)
PackageVulnerable rangeFixed inDependents
tensorflow0.12.0 ... 2.4.1 (98 versions)2.4.2—
tensorflow-cpu1.15.0 ... 2.4.1 (13 versions)2.4.2—
tensorflow-gpu0.12.0 ... 2.4.1 (48 versions)2.4.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 51× 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 101 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2021-29530?
CVE-2021-29530 is a low vulnerability published on May 14, 2021. TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a null pointer dereference by providing an invalid permutation to tf.rawops.SparseMatrixSparseCholesky. This is because the…
When was CVE-2021-29530 disclosed?
CVE-2021-29530 was first published in the National Vulnerability Database 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-29530 actively exploited?
CVE-2021-29530 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2021-29530?
CVE-2021-29530 has a CVSS v3 base score of 2.5 (NVD).
How do I remediate CVE-2021-29530?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-29530, 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-29530

Explore →

Is Your Infrastructure Affected by CVE-2021-29530?

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

Start Free Scan →Browse All CVEs