VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

google-cloud-container: vulnerability history, versions and safety

google-cloud-container is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all google-cloud-container vulnerabilities

Vulert verdict on google-cloud-container 2.67.0 i

Updated on 23 Oct 2026

Good news: 2.67.0, the version you would install today, has no known vulnerabilities.

Package health score 86/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 2.67.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.67.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.67.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 45 packages i
  • Stars 5,411 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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 google-cloud-container, 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.67.0 01 Oct 2026 none Apache-2.0 — Details →
2.66.0 03 Sep 2026 none Apache-2.0 — Details →
2.65.0 03 Jun 2026 none Apache-2.0 — Details →
2.64.0 30 Mar 2026 none Apache-2.0 — Details →
2.63.0 29 Jan 2026 none Apache-2.0 — Details →
2.62.0 09 Jan 2026 none Apache-2.0 — Details →
2.61.0 23 Oct 2025 none Apache-2.0 — Details →
2.60.0 17 Oct 2025 none Apache-2.0 — Details →
2.59.0 23 Jul 2025 none Apache-2.0 — Details →
2.58.0 18 Jul 2025 none Apache-2.0 — Details →
2.57.0 26 May 2025 none Apache-2.0 — Details →
2.56.1 17 Mar 2025 none Apache-2.0 — Details →
2.56.0 12 Feb 2025 none Apache-2.0 — Details →
2.55.1 27 Jan 2025 none Apache-2.0 — Details →
2.55.0 13 Dec 2024 none Apache-2.0 — Details →
2.54.0 14 Nov 2024 none Apache-2.0 — Details →
2.53.0 25 Oct 2024 none Apache-2.0 — Details →
2.52.0 10 Oct 2024 none Apache-2.0 — Details →
2.51.0 04 Sep 2024 none Apache-2.0 — Details →
2.50.0 30 Jul 2024 none Apache-2.0 — Details →
2.49.0 11 Jul 2024 none Apache-2.0 — Details →
2.48.0 10 Jul 2024 none Apache-2.0 — Details →
2.47.1 08 Jul 2024 none Apache-2.0 — Details →
2.47.0 10 Jun 2024 none Apache-2.0 — Details →
2.46.0 29 May 2024 none Apache-2.0 — Details →
2.45.0 27 Mar 2024 none Apache-2.0 — Details →
2.44.0 22 Mar 2024 none Apache-2.0 — Details →
2.43.0 07 Mar 2024 none Apache-2.0 — Details →
2.42.0 04 Mar 2024 none Apache-2.0 — Details →
2.41.0 22 Feb 2024 none Apache-2.0 — Details →
2.40.0 07 Feb 2024 none Apache-2.0 — Details →
2.39.0 01 Feb 2024 none Apache-2.0 — Details →
2.38.0 22 Jan 2024 none Apache-2.0 — Details →
2.37.0 04 Jan 2024 none Apache-2.0 — Details →
2.36.0 07 Dec 2023 none Apache-2.0 — Details →
2.36.0rc0 04 Dec 2023 none Apache-2.0 — Details →
2.35.0 29 Nov 2023 none Apache-2.0 — Details →
2.34.0 16 Nov 2023 none Apache-2.0 — Details →
2.33.0 02 Nov 2023 none Apache-2.0 — Details →
2.32.0 02 Oct 2023 none Apache-2.0 — Details →
2.31.0 08 Sep 2023 none Apache-2.0 — Details →
2.30.0 16 Aug 2023 none Apache-2.0 — Details →
2.29.0 09 Aug 2023 none Apache-2.0 — Details →
2.28.0 24 Jul 2023 none Apache-2.0 — Details →
2.27.0 19 Jul 2023 none Apache-2.0 — Details →
2.26.0 05 Jul 2023 none Apache-2.0 — Details →
2.25.0 29 Jun 2023 none Apache-2.0 — Details →
2.24.0 13 Jun 2023 none Apache-2.0 — Details →
2.23.0 06 Jun 2023 none Apache-2.0 — Details →
2.22.0 01 Jun 2023 none Apache-2.0 — Details →
2.21.0 17 Apr 2023 none Apache-2.0 — Details →
2.20.0 11 Apr 2023 none Apache-2.0 — Details →
2.19.0 06 Apr 2023 none Apache-2.0 — Details →
2.18.0 29 Mar 2023 none Apache-2.0 — Details →
2.17.4 01 Mar 2023 none Apache-2.0 — Details →
2.17.3 07 Feb 2023 none Apache-2.0 — Details →
2.17.2 01 Feb 2023 none Apache-2.0 — Details →
2.17.1 23 Jan 2023 none Apache-2.0 — Details →
2.17.0 18 Jan 2023 none Apache-2.0 — Details →
2.16.0 11 Jan 2023 none Apache-2.0 — Details →
2.15.0 09 Jan 2023 none Apache-2.0 — Details →
2.14.0 15 Dec 2022 none Apache-2.0 — Details →
2.13.0 27 Oct 2022 none Apache-2.0 — Details →
2.12.2 10 Oct 2022 none Apache-2.0 — Details →
2.12.1 04 Oct 2022 none Apache-2.0 — Details →
2.12.0 19 Sep 2022 none Apache-2.0 — Details →
2.11.2 15 Aug 2022 none Apache-2.0 — Details →
2.11.1 09 Aug 2022 none Apache-2.0 — Details →
2.11.0 18 Jul 2022 none Apache-2.0 — Details →
1.0.3 09 Jun 2022 none Apache-2.0 — Details →
2.10.8 07 Jun 2022 none Apache-2.0 — Details →
1.0.2 31 Mar 2022 none Apache-2.0 — Details →
2.10.7 22 Mar 2022 none Apache-2.0 — Details →
2.10.6 07 Mar 2022 none Apache-2.0 — Details →
2.10.5 16 Feb 2022 none Apache-2.0 — Details →
2.10.4 14 Feb 2022 none Apache-2.0 — Details →
2.10.3 12 Feb 2022 none Apache-2.0 — Details →
2.10.1 02 Nov 2021 none Apache-2.0 — Details →
2.10.0 13 Oct 2021 none Apache-2.0 — Details →
2.9.0 11 Oct 2021 none Apache-2.0 — Details →
2.8.1 05 Oct 2021 none Apache-2.0 — Details →
2.8.0 24 Sep 2021 none Apache-2.0 — Details →
2.7.1 26 Jul 2021 none Apache-2.0 — Details →
2.7.0 23 Jul 2021 none Apache-2.0 — Details →
2.6.1 21 Jul 2021 none Apache-2.0 — Details →
2.6.0 13 Jul 2021 none Apache-2.0 — Details →
2.5.0 30 Jun 2021 none Apache-2.0 — Details →
2.4.1 17 May 2021 none Apache-2.0 — Details →
2.4.0 25 Mar 2021 none Apache-2.0 — Details →
2.3.1 19 Feb 2021 none Apache-2.0 — Details →
2.3.0 08 Dec 2020 none Apache-2.0 — Details →
2.2.0 17 Nov 2020 none Apache-2.0 — Details →
2.1.0 16 Sep 2020 none Apache-2.0 — Details →
2.0.1 31 Jul 2020 none Apache-2.0 — Details →
2.0.0 16 Jul 2020 none Apache-2.0 — Details →
1.0.1 17 Jun 2020 none Apache-2.0 — Details →
0.5.0 14 Apr 2020 none Apache-2.0 — Details →
0.4.0 11 Feb 2020 none Apache-2.0 — Details →
0.3.0 30 Jul 2019 none Apache-2.0 — Details →
0.2.1 18 Dec 2018 none Apache-2.0 — Details →
0.2.0 05 Dec 2018 none — — Details →
0.1.1 28 Feb 2018 none — — Details →
0.1.0 14 Dec 2017 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for google-cloud-container

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 google-cloud-container

Is google-cloud-container safe to use?

Vulert has no vulnerabilities on record for google-cloud-container in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is google-cloud-container's Vulert package health score?

Vulert scores google-cloud-container 86/100, which reads as healthy. 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 google-cloud-container affected?

No. 2.67.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of google-cloud-container should I use?

2.67.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 google-cloud-container have?

0 vulnerabilities are recorded for google-cloud-container in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new google-cloud-container vulnerabilities disclosed?

0 vulnerabilities were recorded for google-cloud-container in the last 12 months. 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 google-cloud-container 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 google-cloud-container for upcoming vulnerabilities?

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