In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the implementation of SparseFillEmptyRowsGrad uses a double indexing pattern. It is possible for reverse_index_map(i) to be an index outside of bounds of grad_values, thus resulting in a heap buffer overflow. The issue is patched in commit 390611e0d45c5793c7066110af37c8514e6a6c54, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
CVE-2020-15195
This high-severity CVE scores 8.5 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 43% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.5
- EG Score
- 8.5(medium)
- EG Risk
- 43(Track)EG Risk 43/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 computedSeverity85% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 60%
- KEV
- Not listed
Published
September 25, 2020
Last Modified
November 21, 2024
Advisory Details (3)
Auto-updated Sep 2, 2026Heap buffer overflow in SparseFillEmptyRowsGrad · Advisory · tensorflow/tensorflow · GitHub
https://github.com/tensorflow/tensorflow/security/advisories/GHSA-63xm-rx5p-xvqrTensorFlow 2.3.1
Patch available: tensorflow/tensorflow v2.3.1
https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1commit 390611e0d45c (tensorflow/tensorflow)
Patch available: tensorflow/tensorflow v2.13.0 (contains commit 390611e0d45c)
https://github.com/tensorflow/tensorflow/commit/390611e0d45c5793c7066110af37c8514e6a6c54Affected Packages
(3 across 1 ecosystem)
PyPI(3)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| tensorflow | 0.12.0rc0 ... 2.3.0 (77 versions) | 2.3.1 | — |
| tensorflow-cpu | 1.15.0, 2.1.0, 2.1.1, 2.2.0, 2.3.0 | 2.3.1 | — |
| tensorflow-gpu | 0.12.0 ... 2.3.0 (36 versions) | 2.3.1 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 27× 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 155 total refreshes for this CVE.
- 2026-09-18 19:23 UTCEPSS rescore
- 2026-09-17 19:22 UTCEPSS rescore
- 2026-09-17 19:22 UTCEPSS rescore
- 2026-09-16 14:04 UTCEPSS rescore
- 2026-09-15 03:06 UTCEPSS rescore
- 2026-09-15 03:06 UTCEPSS rescore
- 2026-09-13 16:42 UTCEPSS rescore
- 2026-09-12 14:56 UTCEPSS rescore
- 2026-09-11 14:48 UTCEPSS rescore
- 2026-09-11 09:32 UTCEPSS rescore
- 2026-09-10 09:29 UTCEPSS rescore
- 2026-09-08 21:56 UTCEPSS rescore
- 2026-09-07 15:57 UTCEPSS rescore
- 2026-09-06 13:44 UTCEPSS rescore
- 2026-09-05 15:24 UTCEPSS rescore
- 2026-09-04 13:57 UTCEPSS rescore
- 2026-09-04 05:03 UTCEPSS rescore
- 2026-09-02 14:08 UTCEPSS rescore
- 2026-09-01 05:53 UTCOSV refresh
- 2026-09-01 03:32 UTCEPSS rescore
- 2026-08-30 19:14 UTCEPSS rescore
- 2026-08-30 01:18 UTCEPSS rescore
- 2026-08-27 14:21 UTCEPSS rescore
- 2026-08-26 14:42 UTCEPSS rescore
- 2026-08-25 13:45 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-21 23:45 UTCEPSS rescore
- 2026-08-20 22:52 UTCEPSS rescore
- 2026-08-19 17:00 UTCEPSS rescore
- 2026-08-18 13:44 UTCEPSS rescore
- 2026-08-17 13:43 UTCEPSS rescore
- 2026-08-16 14:52 UTCEPSS rescore
- 2026-08-16 02:11 UTCEPSS rescore
- 2026-08-15 05:07 UTCOSV refresh
- 2026-08-15 01:26 UTCEPSS rescore
- 2026-08-13 21:57 UTCEPSS rescore
- 2026-08-12 13:47 UTCEPSS rescore
- 2026-08-09 13:43 UTCEPSS rescore
- 2026-08-08 16:33 UTCEPSS rescore
- 2026-08-07 16:23 UTCEPSS rescore
- 2026-08-06 13:43 UTCEPSS rescore
- 2026-08-05 19:14 UTCEPSS rescore
- 2026-08-04 15:06 UTCEPSS rescore
- 2026-08-04 10:34 UTCEPSS rescore
- 2026-08-03 10:32 UTCEPSS rescore
- 2026-08-02 02:23 UTCEPSS rescore
- 2026-08-01 04:12 UTCEPSS rescore
- 2026-07-30 17:21 UTCOSV refresh
- 2026-07-30 16:25 UTCEPSS rescore
- 2026-07-30 01:27 UTCEPSS rescore
- 2026-07-28 15:32 UTCEPSS rescore
- 2026-07-27 14:06 UTCEPSS rescore
- 2026-07-26 14:51 UTCEPSS rescore
- 2026-07-25 14:15 UTCEPSS rescore
- 2026-07-25 14:14 UTCEPSS rescore
- 2026-07-24 14:14 UTCEPSS rescore
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 01:49 UTCEG score recompute
- 2026-07-22 22:35 UTCEG score recompute
- 2026-07-22 14:05 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-18 10:02 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-15 16:55 UTCEPSS rescore
- 2026-07-15 01:57 UTCEPSS rescore
- 2026-07-13 22:27 UTCEPSS rescore
- 2026-07-13 22:27 UTCEPSS rescore
- 2026-07-13 06:10 UTCEPSS rescore
- 2026-07-13 06:10 UTCEPSS rescore
- 2026-07-13 02:08 UTCOSV refresh
- 2026-07-12 05:44 UTCEPSS rescore
- 2026-07-11 08:25 UTCEPSS rescore
- 2026-07-11 08:25 UTCEPSS rescore
- 2026-07-09 19:07 UTCEPSS rescore
- 2026-07-08 15:12 UTCEPSS rescore
- 2026-07-07 13:43 UTCEPSS rescore
- 2026-07-07 13:43 UTCEPSS rescore
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-06 02:21 UTCEPSS rescore
- 2026-07-06 02:21 UTCEPSS rescore
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-04 06:29 UTCEPSS rescore
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-01 15:03 UTCEPSS rescore
- 2026-06-30 23:20 UTCEPSS rescore
- 2026-06-30 23:20 UTCEPSS rescore
- 2026-06-29 14:04 UTCEPSS rescore
- 2026-06-28 14:05 UTCEPSS rescore
- 2026-06-28 04:54 UTCEPSS rescore
- 2026-06-28 04:54 UTCEPSS rescore
- 2026-06-27 03:06 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-24 14:03 UTCEPSS rescore
Related CVEs(same CWE)
Same CWE
10 shownCWE-119
- CVE-2003-0819EG 10.0EPSS p99HIGH
- CVE-2003-0903EG 10.0EPSS p98HIGH
- CVE-2003-1339EG 10.0EPSS p99HIGH
- CVE-2003-0095EG 10.0EPSS p96HIGH
- CVE-2002-2227EG 10.0HIGH
- CVE-2002-2248EG 10.0EPSS p93HIGH
- CVE-2002-2250EG 10.0EPSS p94HIGH
- CVE-2002-2251EG 10.0EPSS p94HIGH
- CVE-2002-2253EG 10.0EPSS p94HIGH
- CVE-2002-2257EG 10.0EPSS p92HIGH
Frequently asked(5)
What is CVE-2020-15195?
When was CVE-2020-15195 disclosed?
Is CVE-2020-15195 actively exploited?
What is the CVSS score of CVE-2020-15195?
How do I remediate CVE-2020-15195?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-15195
Is Your Infrastructure Affected by CVE-2020-15195?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.