VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

tensorflow-gpu: vulnerability history, versions and safety

tensorflow-gpu is a package in the PyPI ecosystem. Vulert records 422 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
422 vulnerabilities recorded U422
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
125 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tensorflow-gpu vulnerabilities

Vulert verdict on tensorflow-gpu 2.12.0 i

Updated on 22 Oct 2026

Action needed: 2.12.0 has 149 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 Maintaining
  • Popularity Widely used
  • Community Moderate

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.12.0 — affected i
  • Vulnerabilities on record 422 over 7 years · 125 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 87 packages i
  • Stars 201,060 i
  • OpenSSF scorecard 6/10 i
  • Last release 44 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-gpu, 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.12.0 24 Jan 2023 U1 Apache-2.0 Yes Details →
2.11.0 18 Nov 2022 U19 Apache-2.0 Yes Details →
2.10.1 16 Nov 2022 U19 Apache-2.0 Yes Details →
2.9.3 16 Nov 2022 U19 Apache-2.0 Yes Details →
2.8.4 16 Nov 2022 U20 Apache-2.0 Yes Details →
2.11.0rc2 02 Nov 2022 U19 Apache-2.0 Yes Details →
2.11.0rc1 19 Oct 2022 U19 Apache-2.0 Yes Details →
2.11.0rc0 18 Oct 2022 U19 Apache-2.0 Yes Details →
2.10.0 06 Sep 2022 U43 Apache-2.0 Yes Details →
2.9.2 03 Sep 2022 U42 Apache-2.0 Yes Details →
2.8.3 02 Sep 2022 U42 Apache-2.0 Yes Details →
2.7.4 02 Sep 2022 U44 Apache-2.0 Yes Details →
2.10.0rc3 29 Aug 2022 U19 Apache-2.0 Yes Details →
2.10.0rc2 23 Aug 2022 U19 Apache-2.0 Yes Details →
2.10.0rc1 15 Aug 2022 U19 Apache-2.0 Yes Details →
2.10.0rc0 03 Aug 2022 U19 Apache-2.0 Yes Details →
2.9.1 23 May 2022 U43 Apache-2.0 Yes Details →
2.8.2 23 May 2022 U42 Apache-2.0 Yes Details →
2.6.5 23 May 2022 U100 Apache-2.0 Yes Details →
2.7.3 23 May 2022 U45 Apache-2.0 Yes Details →
2.9.0 16 May 2022 U99 Apache-2.0 Yes Details →
2.8.1 16 May 2022 U42 Apache-2.0 Yes Details →
2.7.2 16 May 2022 U45 Apache-2.0 Yes Details →
2.6.4 16 May 2022 U100 Apache-2.0 Yes Details →
2.9.0rc2 04 May 2022 U20 Apache-2.0 Yes Details →
2.9.0rc1 21 Apr 2022 U20 Apache-2.0 Yes Details →
2.9.0rc0 12 Apr 2022 U20 Apache-2.0 Yes Details →
2.7.1 02 Feb 2022 U124 Apache-2.0 Yes Details →
2.6.3 02 Feb 2022 U123 Apache-2.0 Yes Details →
2.5.3 02 Feb 2022 U123 Apache-2.0 Yes Details →
2.8.0 02 Feb 2022 U123 Apache-2.0 Yes Details →
2.8.0rc1 24 Jan 2022 U44 Apache-2.0 Yes Details →
2.8.0rc0 22 Dec 2021 U44 Apache-2.0 Yes Details →
2.7.0 04 Nov 2021 U126 Apache-2.0 Yes Details →
2.6.2 04 Nov 2021 U175 Apache-2.0 Yes Details →
2.6.1 01 Nov 2021 U175 Apache-2.0 Yes Details →
2.5.2 01 Nov 2021 U175 Apache-2.0 Yes Details →
2.4.4 01 Nov 2021 U175 Apache-2.0 Yes Details →
2.7.0rc1 22 Oct 2021 U132 Apache-2.0 Yes Details →
2.7.0rc0 07 Oct 2021 U132 Apache-2.0 Yes Details →
2.6.0 11 Aug 2021 U209 Apache-2.0 Yes Details →
2.5.1 10 Aug 2021 U207 Apache-2.0 Yes Details →
2.4.3 10 Aug 2021 U207 Apache-2.0 Yes Details →
2.3.4 10 Aug 2021 U209 Apache-2.0 Yes Details →
2.2.3 15 Jun 2021 U251 Apache-2.0 Yes Details →
2.4.2 15 Jun 2021 U302 Apache-2.0 Yes Details →
2.3.3 15 Jun 2021 U304 Apache-2.0 Yes Details →
2.1.4 15 Jun 2021 U254 Apache-2.0 Yes Details →
2.5.0 13 May 2021 U207 Apache-2.0 Yes Details →
2.4.1 21 Jan 2021 U373 Apache-2.0 Yes Details →
1.15.5 06 Jan 2021 U324 Apache-2.0 Yes Details →
2.2.2 06 Jan 2021 U321 Apache-2.0 Yes Details →
2.3.2 06 Jan 2021 U375 Apache-2.0 Yes Details →
2.1.3 06 Jan 2021 U324 Apache-2.0 Yes Details →
2.0.4 06 Jan 2021 U324 Apache-2.0 Yes Details →
2.4.0 14 Dec 2020 U373 Apache-2.0 Yes Details →
2.3.1 24 Sep 2020 U380 Apache-2.0 Yes Details →
2.2.1 24 Sep 2020 U326 Apache-2.0 Yes Details →
2.1.2 24 Sep 2020 U329 Apache-2.0 Yes Details →
2.0.3 24 Sep 2020 U329 Apache-2.0 Yes Details →
1.15.4 24 Sep 2020 U329 Apache-2.0 Yes Details →
2.3.0 27 Jul 2020 U405 Apache-2.0 Yes Details →
2.1.1 18 May 2020 U342 Apache-2.0 Yes Details →
2.0.2 18 May 2020 U342 Apache-2.0 Yes Details →
1.15.3 18 May 2020 U342 Apache-2.0 Yes Details →
2.2.0 07 May 2020 U345 Apache-2.0 Yes Details →
1.15.2 26 Jan 2020 U342 Apache-2.0 Yes Details →
2.0.1 26 Jan 2020 U342 Apache-2.0 Yes Details →
2.1.0 08 Jan 2020 U342 Apache-2.0 Yes Details →
1.15.0 16 Oct 2019 U343 Apache-2.0 Yes Details →
2.0.0 30 Sep 2019 U343 Apache-2.0 Yes Details →
1.13.2 16 Jul 2019 U344 Apache-2.0 Yes Details →
1.14.0 19 Jun 2019 U344 Apache-2.0 Yes Details →
1.13.1 26 Feb 2019 U344 Apache-2.0 Yes Details →
0.12.0 — U350 — Yes Details →
0.12.1 — U350 — Yes Details →
1.0.0 — U351 — Yes Details →
1.0.1 — U351 — Yes Details →
1.1.0 — U351 — Yes Details →
1.10.0 — U345 — Yes Details →
1.10.1 — U345 — Yes Details →
1.11.0 — U345 — Yes Details →
1.12.0 — U345 — Yes Details →
1.12.2 — U344 — Yes Details →
1.12.3 — U344 — Yes Details →
1.2.0 — U351 — Yes Details →
1.2.1 — U351 — Yes Details →
1.3.0 — U351 — Yes Details →
1.4.0 — U351 — Yes Details →
1.4.1 — U351 — Yes Details →
1.5.0 — U351 — Yes Details →
1.5.1 — U351 — Yes Details →
1.6.0 — U351 — Yes Details →
1.7.0 — U349 — Yes Details →
1.7.1 — U345 — Yes Details →
1.8.0 — U345 — Yes Details →
1.9.0 — U345 — 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 125

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

03 Vulnerabilities

Recorded vulnerabilities for tensorflow-gpu

The 5 most severe of 422 vulnerabilities recorded for this package

Search all 422 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-25668: TensorFlow GPU Heap Out-of-Buffer Read Vulnerability 9.8 critical 2.11.1 29 Jun 2026
CVE-2022-23594: TensorFlow GPU Out of Bounds Read Vulnerability 8.8 high 2.7.1 02 Jul 2026
CVE-2023-25801: TensorFlow GPU Double Free Vulnerability in Fractional Pooling 8.0 high 2.11.1 07 Jul 2026
CVE-2022-29216: TensorFlow Code Injection Vulnerability in saved_model_cli 7.8 high 2.6.4 06 Jul 2026
CVE-2023-25670: TensorFlow GPU Null Pointer Error in QuantizedMatMulWithBiasAndDequantize 7.5 high 2.11.1 07 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-gpu

Is tensorflow-gpu safe to use?

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

Vulert scores tensorflow-gpu 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-gpu affected?

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

Which version of tensorflow-gpu should I use?

2.12.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-gpu have?

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

125 vulnerabilities were recorded for tensorflow-gpu 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-gpu 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-gpu for upcoming vulnerabilities?

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