CVE-2020-15202

CRITICALNVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 1.3% (69th 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
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 9.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the Shard API in TensorFlow expects the last argument to be a function taking two int64 (i.e., long long) arguments. However, there are several places in TensorFlow where a lambda taking int or int32 arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption. The issue is patched in commits 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
46
EG Risk 46/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
Severity90% × 45%
Exploitation1% × 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
1.3%
EPSS %ILE
69th
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 total (CVSS ≥ 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

September 25, 2020

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Jul 26, 2026
Patch available. Sources: github_commit, github_release, github.
githubMentions a patch (unverified)

Integer truncation in Shard API usage · Advisory · tensorflow/tensorflow · GitHub

https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4
github_release Patch Available

TensorFlow 2.3.1

Patch available: tensorflow/tensorflow v2.3.1

https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1
github_commit Patch Available

commit ca8c013b5e97 (tensorflow/tensorflow)

Patch available: tensorflow/tensorflow v2.13.0 (contains commit ca8c013b5e97)

https://github.com/tensorflow/tensorflow/commit/ca8c013b5e97b1373b3bb1c97ea655e69f31a575
github_commit Patch Available

commit 27b417360cbd (tensorflow/tensorflow)

Patch available: tensorflow/tensorflow v2.13.0 (contains commit 27b417360cbd)

https://github.com/tensorflow/tensorflow/commit/27b417360cbd671ef55915e4bb6bb06af8b8a832

Affected Packages

(3 across 1 ecosystem)
PyPI(3)
PackageVulnerable rangeFix by version rangeDependents
tensorflow0.12.0rc0 ... 2.3.0 (77 versions)
  • every version up to 1.15.4: fixed in 1.15.4
  • 2.0.0 up to 2.0.3: fixed in 2.0.3
  • 2.1.0 up to 2.1.2: fixed in 2.1.2
  • 2.2.0 up to 2.2.1: fixed in 2.2.1
  • 2.3.0 up to 2.3.1: fixed in 2.3.1
—
tensorflow-cpu1.15.0, 2.1.0, 2.1.1, 2.2.0, 2.3.0
  • every version up to 1.15.4: fixed in 1.15.4
  • 2.0.0 up to 2.0.3: fixed in 2.0.3
  • 2.1.0 up to 2.1.2: fixed in 2.1.2
  • 2.2.0 up to 2.2.1: fixed in 2.2.1
  • 2.3.0 up to 2.3.1: fixed in 2.3.1
—
tensorflow-gpu0.12.0 ... 2.3.0 (36 versions)
  • every version up to 1.15.4: fixed in 1.15.4
  • 2.0.0 up to 2.0.3: fixed in 2.0.3
  • 2.1.0 up to 2.1.2: fixed in 2.1.2
  • 2.2.0 up to 2.2.1: fixed in 2.2.1
  • 2.3.0 up to 2.3.1: fixed in 2.3.1
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2020-15202?
CVE-2020-15202 is a critical vulnerability published on September 25, 2020. In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the Shard API in TensorFlow expects the last argument to be a function taking two int64 (i.e., long long) arguments. However, there are several places in TensorFlow where a lambda taking int or int32 arguments is being used. In…
When was CVE-2020-15202 disclosed?
CVE-2020-15202 was first published on September 25, 2020, 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-2020-15202 actively exploited?
CVE-2020-15202 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (69th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-15202?
CVE-2020-15202 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2020-15202?
A fix for CVE-2020-15202 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-2020-15202

Explore →

Is Your Infrastructure Affected by CVE-2020-15202?

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

Book a Demo →Browse All CVEs