Vulnerability Database · PyPI · Package report

google-api-core: vulnerability history, versions and safety

google-api-core 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.

Vulert verdict on google-api-core 2.43.0 i

Updated on 23 Oct 2026

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

Package health score 89/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 2.43.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 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-api-core, 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.43.0 22 Oct 2026 none Apache-2.0 — Details →
2.42.0 08 Oct 2026 none Apache-2.0 — Details →
2.41.0 05 Oct 2026 none Apache-2.0 — Details →
2.40.0 29 Sep 2026 none Apache-2.0 — Details →
2.39.0 24 Sep 2026 none Apache-2.0 — Details →
2.38.0 17 Sep 2026 none Apache-2.0 — Details →
2.37.0 14 Sep 2026 none Apache-2.0 — Details →
2.36.0 03 Sep 2026 none Apache-2.0 — Details →
2.35.0 24 Aug 2026 none Apache-2.0 — Details →
2.34.0 06 Aug 2026 none Apache-2.0 — Details →
2.33.0 22 Jul 2026 none Apache-2.0 — Details →
2.32.0 16 Jul 2026 none Apache-2.0 — Details →
2.31.0 03 Jun 2026 none Apache-2.0 — Details →
2.30.3 09 Apr 2026 none Apache-2.0 — Details →
2.30.2 02 Apr 2026 none Apache-2.0 — Details →
2.30.1 30 Mar 2026 none Apache-2.0 — Details →
2.30.0 18 Feb 2026 none Apache-2.0 — Details →
2.29.0 08 Jan 2026 none Apache-2.0 — Details →
2.28.1 28 Oct 2025 none Apache-2.0 — Details →
2.28.0 27 Oct 2025 none Apache-2.0 — Details →
2.27.0 22 Oct 2025 none Apache-2.0 — Details →
2.26.0 08 Oct 2025 none Apache-2.0 — Details →
2.25.2 03 Oct 2025 none Apache-2.0 — Details →
2.25.1 12 Jun 2025 none Apache-2.0 — Details →
2.25.1rc0 12 Jun 2025 none Apache-2.0 — Details →
2.25.0 02 Jun 2025 none Apache-2.0 — Details →
2.25.0rc1 07 May 2025 none Apache-2.0 — Details →
2.25.0rc0 23 Apr 2025 none Apache-2.0 — Details →
2.24.2 10 Mar 2025 none Apache-2.0 — Details →
2.24.1 27 Jan 2025 none Apache-2.0 — Details →
2.24.1rc1 24 Jan 2025 none Apache-2.0 — Details →
2.24.1rc0 17 Jan 2025 none Apache-2.0 — Details →
2.24.0 09 Dec 2024 none Apache-2.0 — Details →
2.23.0 11 Nov 2024 none Apache-2.0 — Details →
2.23.0rc0 28 Oct 2024 none Apache-2.0 — Details →
2.22.0 28 Oct 2024 none Apache-2.0 — Details →
2.22.0rc0 23 Oct 2024 none Apache-2.0 — Details →
2.21.0 09 Oct 2024 none Apache-2.0 — Details →
2.21.0rc0 08 Oct 2024 none Apache-2.0 — Details →
2.20.1rc0 26 Sep 2024 none Apache-2.0 — Details →
2.20.0 19 Sep 2024 none Apache-2.0 — Details →
2.20.0rc0 12 Sep 2024 none Apache-2.0 — Details →
2.19.2 27 Aug 2024 none Apache-2.0 — Details →
2.19.1 24 Jun 2024 none Apache-2.0 — Details →
2.19.1rc0 19 Jun 2024 none Apache-2.0 — Details →
2.19.0 30 Apr 2024 none Apache-2.0 — Details →
2.19.0rc0 29 Apr 2024 none Apache-2.0 — Details →
2.18.0 21 Mar 2024 none Apache-2.0 — Details →
2.18.0rc0 20 Mar 2024 none Apache-2.0 — Details →
2.17.1 14 Feb 2024 none Apache-2.0 — Details →
1.34.1 14 Feb 2024 none Apache-2.0 — Details →
1.34.1rc1 13 Feb 2024 none Apache-2.0 — Details →
2.17.1rc1 13 Feb 2024 none Apache-2.0 — Details →
2.17.0 08 Feb 2024 none Apache-2.0 — Details →
2.17.0rc0 06 Feb 2024 none Apache-2.0 — Details →
2.16.2 02 Feb 2024 none Apache-2.0 — Details →
2.16.1 30 Jan 2024 none Apache-2.0 — Details →
2.16.0 29 Jan 2024 none Apache-2.0 — Details →
2.16.0rc0 13 Dec 2023 none Apache-2.0 — Details →
2.15.0 07 Dec 2023 none Apache-2.0 — Details →
2.15.0rc1 04 Dec 2023 none Apache-2.0 — Details →
2.14.0 09 Nov 2023 none Apache-2.0 — Details →
2.13.1 09 Nov 2023 none Apache-2.0 — Details →
2.13.0 07 Nov 2023 none Apache-2.0 — Details →
2.13.0rc1 02 Nov 2023 none Apache-2.0 — Details →
2.12.0 25 Sep 2023 none Apache-2.0 — Details →
2.12.0rc1 11 Sep 2023 none Apache-2.0 — Details →
2.12.0.dev1 16 Aug 2023 none Apache-2.0 — Details →
2.12.0.dev0 21 Jun 2023 none Apache-2.0 — Details →
2.11.1 14 Jun 2023 none Apache-2.0 — Details →
2.11.1rc1 12 Jun 2023 none Apache-2.0 — Details →
1.34.0 01 Dec 2022 none Apache-2.0 — Details →
2.11.0 01 Dec 2022 none Apache-2.0 — Details →
2.11.0rc1 10 Nov 2022 none Apache-2.0 — Details →
1.33.2 10 Oct 2022 none Apache-2.0 — Details →
2.10.2 08 Oct 2022 none Apache-2.0 — Details →
1.33.1 15 Sep 2022 none Apache-2.0 — Details →
2.10.1 14 Sep 2022 none Apache-2.0 — Details →
1.33.0 07 Sep 2022 none Apache-2.0 — Details →
1.33.0b1 06 Sep 2022 none Apache-2.0 — Details →
2.10.0 02 Sep 2022 none Apache-2.0 — Details →
2.9.0 02 Sep 2022 none Apache-2.0 — Details →
1.32.0 13 Jul 2022 none Apache-2.0 — Details →
2.8.2 15 Jun 2022 none Apache-2.0 — Details →
1.31.6 27 May 2022 none Apache-2.0 — Details →
2.8.1 26 May 2022 none Apache-2.0 — Details →
2.8.0 18 May 2022 none Apache-2.0 — Details →
2.7.3 02 May 2022 none Apache-2.0 — Details →
2.7.2 13 Apr 2022 none Apache-2.0 — Details →
2.7.1 09 Mar 2022 none Apache-2.0 — Details →
2.7.0 08 Mar 2022 none Apache-2.0 — Details →
2.6.1 07 Mar 2022 none Apache-2.0 — Details →
2.6.0 03 Mar 2022 none Apache-2.0 — Details →
2.5.0 02 Feb 2022 none Apache-2.0 — Details →
2.4.0 11 Jan 2022 none Apache-2.0 — Details →
2.3.2 16 Dec 2021 none Apache-2.0 — Details →
1.31.5 15 Dec 2021 none Apache-2.0 — Details →
2.3.1 15 Dec 2021 none Apache-2.0 — Details →
2.3.0 07 Dec 2021 none Apache-2.0 — Details →
1.31.4 08 Nov 2021 none Apache-2.0 — Details →
2.2.2 02 Nov 2021 none — — Details →
2.2.1 28 Oct 2021 none — — Details →
2.2.0 26 Oct 2021 none — — Details →
2.1.1 13 Oct 2021 none — — Details →
2.1.0 05 Oct 2021 none — — Details →
1.31.3 20 Sep 2021 none — — Details →
2.0.1 31 Aug 2021 none — — Details →
2.0.0 18 Aug 2021 none — — Details →
1.31.2 16 Aug 2021 none — — Details →
2.0.0b1 03 Aug 2021 none — — Details →
1.31.1 27 Jul 2021 none — — Details →
1.31.0 09 Jul 2021 none — — Details →
1.30.0 08 Jun 2021 none — — Details →
1.29.0 03 Jun 2021 none — — Details →
1.28.0 20 May 2021 none — — Details →
1.27.0 18 May 2021 none — — Details →
1.26.3 29 Mar 2021 none — — Details →
1.26.2 23 Mar 2021 none — — Details →
1.26.1 04 Mar 2021 none — — Details →
1.26.0 08 Feb 2021 none — — Details →

The newest 120 of 173 versions Vulert tracks. 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-api-core

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-api-core

Is google-api-core safe to use?

Vulert has no vulnerabilities on record for google-api-core 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-api-core's Vulert package health score?

Vulert scores google-api-core 89/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-api-core affected?

No. 2.43.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.

How many vulnerabilities does google-api-core have?

0 vulnerabilities are recorded for google-api-core 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-api-core vulnerabilities disclosed?

0 vulnerabilities were recorded for google-api-core 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-api-core 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-api-core for upcoming vulnerabilities?

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