VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

tensorflow-cpu: vulnerability history, versions and safety

tensorflow-cpu is a package in the PyPI ecosystem. Vulert records 423 vulnerabilities for it across 97 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
423 vulnerabilities recorded U423
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
126 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-cpu vulnerabilities

Vulert verdict on tensorflow-cpu 2.21.0 i

Updated on 22 Oct 2026

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

Package health score 42/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • 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 423 over 7 years · 126 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 67 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-cpu, 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 23 Sep 2026 U148 Apache-2.0 Yes Details →
2.21.0 06 Mar 2026 U148 Apache-2.0 Yes Details →
2.21.0rc1 02 Mar 2026 U148 Apache-2.0 Yes Details →
2.21.0rc0 09 Feb 2026 U148 Apache-2.0 Yes Details →
2.20.0 13 Aug 2025 U148 Apache-2.0 Yes Details →
2.19.1 13 Aug 2025 U148 Apache-2.0 Yes Details →
2.20.0rc0 29 Jul 2025 U148 Apache-2.0 Yes Details →
2.19.0 12 Mar 2025 U148 Apache-2.0 Yes Details →
2.18.1 12 Mar 2025 U148 Apache-2.0 Yes Details →
2.19.0rc0 21 Feb 2025 U148 Apache-2.0 Yes Details →
2.18.0 25 Oct 2024 U148 Apache-2.0 Yes Details →
2.17.1 24 Oct 2024 U148 Apache-2.0 Yes Details →
2.18.0rc2 16 Oct 2024 U148 Apache-2.0 Yes Details →
2.18.0rc1 07 Oct 2024 U148 Apache-2.0 Yes Details →
2.18.0rc0 30 Sep 2024 U148 Apache-2.0 Yes Details →
2.17.0 11 Jul 2024 U148 Apache-2.0 Yes Details →
2.17.0rc1 02 Jul 2024 U148 Apache-2.0 Yes Details →
2.16.2 28 Jun 2024 U148 Apache-2.0 Yes Details →
2.17.0rc0 18 Jun 2024 U148 Apache-2.0 Yes Details →
2.16.1 09 Mar 2024 U148 Apache-2.0 Yes Details →
2.15.1 08 Mar 2024 U148 Apache-2.0 Yes Details →
2.16.0rc0 23 Feb 2024 U148 Apache-2.0 Yes Details →
2.15.0.post1 05 Dec 2023 U148 Apache-2.0 Yes Details →
2.15.0 14 Nov 2023 U148 Apache-2.0 Yes Details →
2.14.1 14 Nov 2023 U148 Apache-2.0 Yes Details →
2.15.0rc1 03 Nov 2023 U148 Apache-2.0 Yes Details →
2.15.0rc0 25 Oct 2023 U148 Apache-2.0 Yes Details →
2.14.0 26 Sep 2023 U148 Apache-2.0 Yes Details →
2.13.1 26 Sep 2023 U148 Apache-2.0 Yes Details →
2.14.0rc1 01 Sep 2023 U148 Apache-2.0 Yes Details →
2.14.0rc0 17 Aug 2023 U148 Apache-2.0 Yes Details →
2.13.0 05 Jul 2023 U148 Apache-2.0 Yes Details →
2.12.1 05 Jul 2023 U148 Apache-2.0 Yes Details →
2.13.0rc2 22 Jun 2023 U148 Apache-2.0 Yes Details →
2.13.0rc1 30 May 2023 U148 Apache-2.0 Yes Details →
2.13.0rc0 10 May 2023 U148 Apache-2.0 Yes Details →
2.12.0 22 Mar 2023 U1 Apache-2.0 Yes Details →
2.11.1 20 Mar 2023 U1 Apache-2.0 Yes Details →
2.12.0rc1 07 Mar 2023 U1 Apache-2.0 Yes Details →
2.12.0rc0 15 Feb 2023 U1 Apache-2.0 Yes Details →
2.11.0 18 Nov 2022 U22 Apache-2.0 Yes Details →
2.10.1 16 Nov 2022 U22 Apache-2.0 Yes Details →
2.9.3 16 Nov 2022 U22 Apache-2.0 Yes Details →
2.8.4 16 Nov 2022 U23 Apache-2.0 Yes Details →
2.11.0rc2 02 Nov 2022 U22 Apache-2.0 Yes Details →
2.11.0rc1 19 Oct 2022 U22 Apache-2.0 Yes Details →
2.11.0rc0 18 Oct 2022 U22 Apache-2.0 Yes Details →
2.10.0 06 Sep 2022 U44 Apache-2.0 Yes Details →
2.9.2 03 Sep 2022 U43 Apache-2.0 Yes Details →
2.8.3 02 Sep 2022 U43 Apache-2.0 Yes Details →
2.7.4 02 Sep 2022 U45 Apache-2.0 Yes Details →
2.10.0rc3 29 Aug 2022 U22 Apache-2.0 Yes Details →
2.10.0rc2 23 Aug 2022 U22 Apache-2.0 Yes Details →
2.10.0rc1 15 Aug 2022 U22 Apache-2.0 Yes Details →
2.10.0rc0 03 Aug 2022 U22 Apache-2.0 Yes Details →
2.9.1 23 May 2022 U44 Apache-2.0 Yes Details →
2.8.2 23 May 2022 U43 Apache-2.0 Yes Details →
2.6.5 23 May 2022 U101 Apache-2.0 Yes Details →
2.7.3 23 May 2022 U46 Apache-2.0 Yes Details →
2.9.0 16 May 2022 U100 Apache-2.0 Yes Details →
2.8.1 16 May 2022 U43 Apache-2.0 Yes Details →
2.7.2 16 May 2022 U46 Apache-2.0 Yes Details →
2.6.4 16 May 2022 U101 Apache-2.0 Yes Details →
2.9.0rc2 04 May 2022 U23 Apache-2.0 Yes Details →
2.9.0rc1 26 Apr 2022 U23 Apache-2.0 Yes Details →
2.9.0rc0 12 Apr 2022 U23 Apache-2.0 Yes Details →
2.7.1 02 Feb 2022 U125 Apache-2.0 Yes Details →
2.6.3 02 Feb 2022 U124 Apache-2.0 Yes Details →
2.5.3 02 Feb 2022 U124 Apache-2.0 Yes Details →
2.8.0 02 Feb 2022 U124 Apache-2.0 Yes Details →
2.7.0 04 Nov 2021 U127 Apache-2.0 Yes Details →
2.6.2 04 Nov 2021 U176 Apache-2.0 Yes Details →
2.6.1 01 Nov 2021 U176 Apache-2.0 Yes Details →
2.5.2 01 Nov 2021 U176 Apache-2.0 Yes Details →
2.4.4 01 Nov 2021 U176 Apache-2.0 Yes Details →
2.6.0 11 Aug 2021 U210 Apache-2.0 Yes Details →
2.5.1 10 Aug 2021 U208 Apache-2.0 Yes Details →
2.4.3 10 Aug 2021 U208 Apache-2.0 Yes Details →
2.3.4 10 Aug 2021 U210 Apache-2.0 Yes Details →
2.2.3 15 Jun 2021 U252 Apache-2.0 Yes Details →
2.4.2 15 Jun 2021 U303 Apache-2.0 Yes Details →
2.3.3 15 Jun 2021 U305 Apache-2.0 Yes Details →
2.1.4 15 Jun 2021 U255 Apache-2.0 Yes Details →
2.5.0 13 May 2021 U208 Apache-2.0 Yes Details →
2.4.1 21 Jan 2021 U374 Apache-2.0 Yes Details →
2.3.2 06 Jan 2021 U376 Apache-2.0 Yes Details →
2.2.2 06 Jan 2021 U322 Apache-2.0 Yes Details →
2.1.3 06 Jan 2021 U325 Apache-2.0 Yes Details →
2.4.0 14 Dec 2020 U374 Apache-2.0 Yes Details →
2.3.1 24 Sep 2020 U381 Apache-2.0 Yes Details →
2.2.1 24 Sep 2020 U327 Apache-2.0 Yes Details →
2.1.2 24 Sep 2020 U330 Apache-2.0 Yes Details →
2.3.0 27 Jul 2020 U406 Apache-2.0 Yes Details →
2.1.1 18 May 2020 U343 Apache-2.0 Yes Details →
2.2.0 07 May 2020 U346 Apache-2.0 Yes Details →
2.1.0 08 Jan 2020 U343 Apache-2.0 Yes Details →
1.15.0 16 Oct 2019 U344 Apache-2.0 Yes Details →

All 97 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 7
  • 2020 35
  • 2021 200
  • 2022 55
  • 2026 126

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

03 Vulnerabilities

Recorded vulnerabilities for tensorflow-cpu

The 5 most severe of 423 vulnerabilities recorded for this package

Search all 423 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-25668: TensorFlow CPU Heap Out-of-Buffer Read Vulnerability 9.8 critical 2.11.1 29 Jun 2026
CVE-2022-23594: TensorFlow CPU Out of Bounds Read Vulnerability 8.8 high 2.7.1 09 Jul 2026
CVE-2023-25801: TensorFlow Double Free Vulnerability in Fractional Pooling Operations 8.0 high 2.11.1 13 Jul 2026
CVE-2022-29216: TensorFlow Code Injection Vulnerability in saved_model_cli 7.8 high 2.6.4 09 Jul 2026
CVE-2023-25670: TensorFlow CPU Null Pointer Error in QuantizedMatMulWithBiasAndDequantize 7.5 high 2.11.1 13 Jul 2026

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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-cpu

Is tensorflow-cpu safe to use?

Vulert records 423 vulnerabilities for tensorflow-cpu in PyPI: 0 critical, 0 high, 0 medium and 0 low, plus 423 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-cpu's Vulert package health score?

Vulert scores tensorflow-cpu 42/100, which reads as risky. 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-cpu affected?

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

Which version of tensorflow-cpu 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-cpu have?

423 vulnerabilities are recorded for tensorflow-cpu in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 423 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-cpu vulnerabilities disclosed?

126 vulnerabilities were recorded for tensorflow-cpu 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-cpu 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-cpu for upcoming vulnerabilities?

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