VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

tensorflow: vulnerability history, versions and safety

tensorflow is a package in the PyPI ecosystem. Vulert records 862 vulnerabilities for it across 120 releases, from Apr 2019 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
862 vulnerabilities recorded C6 H123 M200 L105 U428
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
185 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tensorflow vulnerabilities

Vulert verdict on tensorflow 2.21.0 i

Updated on 23 Oct 2026

Action needed: 2.21.0 has 122 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 2.21.0 — affected i
  • Vulnerabilities on record 862 over 7 years · 185 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 3,403 packages i
  • Last release 7 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for tensorflow, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.22.0rc0 22 Sep 2026 U122 Apache-2.0 Yes Details →
2.21.0 06 Mar 2026 U122 Apache-2.0 Yes Details →
2.21.0rc1 02 Mar 2026 U122 Apache-2.0 Yes Details →
2.21.0rc0 09 Feb 2026 U122 Apache-2.0 Yes Details →
2.20.0 13 Aug 2025 U122 Apache-2.0 Yes Details →
2.19.1 13 Aug 2025 U122 Apache-2.0 Yes Details →
2.20.0rc0 29 Jul 2025 U122 Apache-2.0 Yes Details →
2.19.0 12 Mar 2025 U122 Apache-2.0 Yes Details →
2.18.1 12 Mar 2025 U122 Apache-2.0 Yes Details →
2.19.0rc0 21 Feb 2025 U122 Apache-2.0 Yes Details →
2.18.0 25 Oct 2024 U122 Apache-2.0 Yes Details →
2.17.1 24 Oct 2024 U122 Apache-2.0 Yes Details →
2.18.0rc2 16 Oct 2024 U122 Apache-2.0 Yes Details →
2.18.0rc1 07 Oct 2024 U122 Apache-2.0 Yes Details →
2.18.0rc0 30 Sep 2024 U122 Apache-2.0 Yes Details →
2.17.0 11 Jul 2024 U122 Apache-2.0 Yes Details →
2.17.0rc1 02 Jul 2024 U122 Apache-2.0 Yes Details →
2.16.2 28 Jun 2024 U122 Apache-2.0 Yes Details →
2.17.0rc0 18 Jun 2024 U122 Apache-2.0 Yes Details →
2.16.1 09 Mar 2024 U122 Apache-2.0 Yes Details →
2.15.1 08 Mar 2024 U122 Apache-2.0 Yes Details →
2.16.0rc0 23 Feb 2024 U122 Apache-2.0 Yes Details →
2.15.0.post1 05 Dec 2023 U122 Apache-2.0 Yes Details →
2.15.0 14 Nov 2023 U122 Apache-2.0 Yes Details →
2.14.1 14 Nov 2023 U122 Apache-2.0 Yes Details →
2.15.0rc1 03 Nov 2023 U122 Apache-2.0 Yes Details →
2.15.0rc0 25 Oct 2023 U122 Apache-2.0 Yes Details →
2.14.0 26 Sep 2023 U122 Apache-2.0 Yes Details →
2.13.1 26 Sep 2023 U122 Apache-2.0 Yes Details →
2.14.0rc1 01 Sep 2023 U122 Apache-2.0 Yes Details →
2.14.0rc0 17 Aug 2023 U122 Apache-2.0 Yes Details →
2.13.0 05 Jul 2023 U122 Apache-2.0 Yes Details →
2.12.1 05 Jul 2023 U122 Apache-2.0 Yes Details →
2.13.0rc2 22 Jun 2023 U122 Apache-2.0 Yes Details →
2.13.0rc1 30 May 2023 U122 Apache-2.0 Yes Details →
2.13.0rc0 10 May 2023 U122 Apache-2.0 Yes Details →
2.12.0 22 Mar 2023 H1 U1 Apache-2.0 Yes Details →
2.11.1 20 Mar 2023 H1 U1 Apache-2.0 Yes Details →
2.12.0rc1 07 Mar 2023 H1 U1 Apache-2.0 Yes Details →
2.12.0rc0 15 Feb 2023 H1 U1 Apache-2.0 Yes Details →
2.11.0 18 Nov 2022 C1 H19 M2 U22 Apache-2.0 Yes Details →
2.10.1 16 Nov 2022 C1 H19 M2 U22 Apache-2.0 Yes Details →
2.9.3 16 Nov 2022 C1 H19 M2 U22 Apache-2.0 Yes Details →
2.8.4 16 Nov 2022 C1 H19 M3 U23 Apache-2.0 Yes Details →
2.11.0rc2 02 Nov 2022 C1 H19 M2 U22 Apache-2.0 Yes Details →
2.11.0rc1 19 Oct 2022 C1 H19 M2 U22 Apache-2.0 Yes Details →
2.11.0rc0 18 Oct 2022 C1 H19 M2 U22 Apache-2.0 Yes Details →
2.10.0 06 Sep 2022 C1 H19 M4 U46 Apache-2.0 Yes Details →
2.9.2 03 Sep 2022 C1 H19 M3 U45 Apache-2.0 Yes Details →
2.8.3 02 Sep 2022 C1 H22 M21 L2 U45 Apache-2.0 Yes Details →
2.7.4 02 Sep 2022 C1 H22 M21 L2 U45 Apache-2.0 Yes Details →
2.10.0rc3 29 Aug 2022 C1 H19 M2 U22 Apache-2.0 Yes Details →
2.10.0rc2 23 Aug 2022 C1 H19 M2 U22 Apache-2.0 Yes Details →
2.10.0rc1 15 Aug 2022 C1 H19 M2 U22 Apache-2.0 Yes Details →
2.10.0rc0 03 Aug 2022 C1 H19 M2 U22 Apache-2.0 Yes Details →
2.9.1 23 May 2022 C1 H19 M3 U46 Apache-2.0 Yes Details →
2.8.2 23 May 2022 C1 H22 M21 L2 U45 Apache-2.0 Yes Details →
2.6.5 23 May 2022 C1 H24 M77 L4 U105 Apache-2.0 Yes Details →
2.7.3 23 May 2022 C1 H22 M22 L2 U46 Apache-2.0 Yes Details →
2.9.0 16 May 2022 C1 H19 M3 U104 Apache-2.0 Yes Details →
2.8.1 16 May 2022 C1 H22 M21 L2 U45 Apache-2.0 Yes Details →
2.7.2 16 May 2022 C1 H22 M22 L2 U46 Apache-2.0 Yes Details →
2.6.4 16 May 2022 C1 H24 M77 L4 U105 Apache-2.0 Yes Details →
2.9.0rc2 04 May 2022 C1 H19 M3 U23 Apache-2.0 Yes Details →
2.9.0rc1 21 Apr 2022 C1 H19 M3 U23 Apache-2.0 Yes Details →
2.9.0rc0 12 Apr 2022 C1 H19 M3 U23 Apache-2.0 Yes Details →
2.7.1 02 Feb 2022 C1 H24 M76 L4 U127 Apache-2.0 Yes Details →
2.6.3 02 Feb 2022 C1 H26 M99 L4 U128 Apache-2.0 Yes Details →
2.5.3 02 Feb 2022 C1 H26 M99 L4 U128 Apache-2.0 Yes Details →
2.8.0 02 Feb 2022 C1 H22 M22 L2 U128 Apache-2.0 Yes Details →
2.8.0rc1 24 Jan 2022 C1 H24 M21 L2 U47 Apache-2.0 Yes Details →
2.8.0rc0 22 Dec 2021 C1 H24 M21 L2 U47 Apache-2.0 Yes Details →
2.7.0 04 Nov 2021 C1 H25 M77 L4 U181 Apache-2.0 Yes Details →
2.6.2 04 Nov 2021 C1 H26 M99 L4 U180 Apache-2.0 Yes Details →
2.6.1 01 Nov 2021 C1 H26 M99 L4 U180 Apache-2.0 Yes Details →
2.5.2 01 Nov 2021 C2 H65 M114 L4 U180 Apache-2.0 Yes Details →
2.4.4 01 Nov 2021 C2 H65 M114 L4 U180 Apache-2.0 Yes Details →
2.7.0rc1 22 Oct 2021 C1 H24 M77 L4 U137 Apache-2.0 Yes Details →
2.7.0rc0 07 Oct 2021 C1 H24 M77 L4 U137 Apache-2.0 Yes Details →
2.6.0 11 Aug 2021 C2 H36 M121 L4 U214 Apache-2.0 Yes Details →
2.5.1 10 Aug 2021 C2 H65 M115 L4 U212 Apache-2.0 Yes Details →
2.4.3 10 Aug 2021 C2 H65 M114 L4 U212 Apache-2.0 Yes Details →
2.3.4 10 Aug 2021 C2 H66 M116 L4 U214 Apache-2.0 Yes Details →
2.6.0rc2 04 Aug 2021 C1 H26 M99 L4 U128 Apache-2.0 Yes Details →
2.6.0rc1 13 Jul 2021 C1 H26 M100 L4 U128 Apache-2.0 Yes Details →
2.6.0rc0 29 Jun 2021 C1 H26 M100 L4 U128 Apache-2.0 Yes Details →
2.2.3 15 Jun 2021 C2 H92 M145 L4 U256 Apache-2.0 Yes Details →
2.4.2 15 Jun 2021 C2 H65 M115 L4 U307 Apache-2.0 Yes Details →
2.3.3 15 Jun 2021 C2 H92 M145 L4 U309 Apache-2.0 Yes Details →
2.1.4 15 Jun 2021 C2 H92 M145 L4 U259 Apache-2.0 Yes Details →
2.5.0 13 May 2021 C2 H65 M116 L4 U212 Apache-2.0 Yes Details →
2.4.1 21 Jan 2021 C2 H65 M115 L5 U378 Apache-2.0 Yes Details →
1.15.5 06 Jan 2021 C2 H93 M154 L96 U329 Apache-2.0 Yes Details →
2.2.2 06 Jan 2021 C2 H92 M145 L4 U326 Apache-2.0 Yes Details →
2.3.2 06 Jan 2021 C2 H92 M145 L9 U380 Apache-2.0 Yes Details →
2.1.3 06 Jan 2021 C2 H93 M154 L96 U329 Apache-2.0 Yes Details →
2.0.4 06 Jan 2021 C2 H93 M154 L96 U329 Apache-2.0 Yes Details →
2.4.0 14 Dec 2020 C2 H65 M115 L5 U378 Apache-2.0 Yes Details →
2.3.1 24 Sep 2020 C2 H92 M145 L9 U385 Apache-2.0 Yes Details →
2.2.1 24 Sep 2020 C2 H92 M145 L4 U331 Apache-2.0 Yes Details →
2.1.2 24 Sep 2020 C2 H93 M154 L96 U334 — Yes Details →
2.0.3 24 Sep 2020 C2 H93 M154 L96 U334 — Yes Details →
1.15.4 24 Sep 2020 C2 H93 M158 L97 U334 — Yes Details →
2.3.0 27 Jul 2020 C2 H94 M149 L9 U410 — Yes Details →
2.1.1 18 May 2020 C2 H93 M154 L96 U347 — Yes Details →
2.0.2 18 May 2020 C2 H93 M154 L96 U347 — Yes Details →
1.15.3 18 May 2020 C2 H99 M165 L97 U347 — Yes Details →
2.2.0 07 May 2020 C4 H93 M148 L4 U350 — Yes Details →
1.15.2 26 Jan 2020 C2 H99 M165 L97 U347 — Yes Details →
2.0.1 26 Jan 2020 C2 H93 M154 L96 U347 — Yes Details →
2.1.0 08 Jan 2020 C2 H93 M154 L96 U347 — Yes Details →
1.15.0 16 Oct 2019 C2 H99 M165 L98 U348 — Yes Details →
2.0.0 30 Sep 2019 C2 H93 M154 L96 U348 — Yes Details →
1.13.2 16 Jul 2019 C2 H99 M165 L99 U349 — Yes Details →
1.14.0 19 Jun 2019 C2 H99 M165 L99 U349 — Yes Details →
1.13.1 26 Feb 2019 C2 H99 M165 L99 U349 — Yes Details →
0.12.0 — C2 H100 M165 L99 U355 — Yes Details →
0.12.1 — C2 H100 M165 L99 U355 — Yes Details →
1.0.0 — C3 H102 M165 L99 U356 — Yes Details →
1.0.1 — C3 H102 M165 L99 U356 — Yes Details →

The newest 120 of 139 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 15
  • 2020 69
  • 2021 400
  • 2022 171
  • 2023 21
  • 2024 1
  • 2026 185

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 185 of the 862 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for tensorflow

The 5 most severe of 862 vulnerabilities recorded for this package

Search all 862 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-25668: TensorFlow Heap Out-of-Buffer Read Vulnerability 9.8 critical 2.11.1 24 Mar 2023
CVE-2018-7575: Integer Overflow or Wraparound in Google TensorFlow 9.8 critical 1.7.1 30 Apr 2019
CVE-2023-25668: TensorFlow Heap Out-of-Bounds Read Vulnerability in QuantizeAndDequantize Operation 9.8 critical 2.11.1 29 Jun 2026
NULL Pointer Dereference and Access of Uninitialized Pointer in TensorFlow 9.3 critical 2.5.3 09 Feb 2022
CVE-2021-37678: Arbitrary code execution due to YAML deserialization in TensorFlow 9.3 high 2.3.4 25 Aug 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About tensorflow

Is tensorflow safe to use?

Vulert records 862 vulnerabilities for tensorflow in PyPI: 6 critical, 123 high, 200 medium and 105 low, plus 428 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is tensorflow's Vulert package health score?

Vulert scores tensorflow 50/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of tensorflow affected?

Yes. 2.21.0, the version you would install today, has 122 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of tensorflow should I use?

2.21.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does tensorflow have?

862 vulnerabilities are recorded for tensorflow in the PyPI ecosystem: 6 critical, 123 high, 200 medium and 105 low, plus 428 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new tensorflow vulnerabilities disclosed?

185 vulnerabilities were recorded for tensorflow in the last 12 months, and the oldest entry in this database dates to 23 Apr 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of tensorflow are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor tensorflow for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the tensorflow version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.