VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

apache-airflow-providers-google: vulnerability history, versions and safety

apache-airflow-providers-google is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 115 releases, from Feb 2023 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded C1 H3 U6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
8 in the last 12 months

Most recent disclosure 29 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all apache-airflow-providers-google vulnerabilities

Vulert verdict on apache-airflow-providers-google 22.7.0 i

Updated on 23 Oct 2026

Good news: 22.7.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 10.

Package health score 63/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 22.7.0 — unaffected i
  • Vulnerabilities on record 10 over 3 years · 8 in the last year i
  • Latest disclosure 29 Sep 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 47,242 i
  • OpenSSF scorecard 5/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 apache-airflow-providers-google, 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
22.8.0rc1 21 Oct 2026 none Apache-2.0 — Details →
22.7.0 17 Oct 2026 none Apache-2.0 — Details →
22.7.0rc2 14 Oct 2026 none Apache-2.0 — Details →
22.7.0rc1 08 Oct 2026 none Apache-2.0 — Details →
22.6.0 29 Sep 2026 none Apache-2.0 — Details →
22.6.0rc1 24 Sep 2026 U1 Apache-2.0 Yes Details →
22.5.0 14 Sep 2026 U1 Apache-2.0 Yes Details →
22.5.0rc1 10 Sep 2026 U1 Apache-2.0 Yes Details →
22.4.0 23 Aug 2026 U1 Apache-2.0 Yes Details →
22.4.0rc1 19 Aug 2026 U1 Apache-2.0 Yes Details →
22.3.0 10 Aug 2026 U1 Apache-2.0 Yes Details →
22.3.0rc4 08 Aug 2026 U2 Apache-2.0 Yes Details →
22.3.0rc3 06 Aug 2026 U2 Apache-2.0 Yes Details →
22.3.0rc2 03 Aug 2026 U2 Apache-2.0 Yes Details →
22.3.0rc1 23 Jul 2026 U2 Apache-2.0 Yes Details →
22.2.2 10 Jul 2026 U2 Apache-2.0 Yes Details →
22.2.2rc1 07 Jul 2026 U2 Apache-2.0 Yes Details →
22.2.1 03 Jul 2026 U2 Apache-2.0 Yes Details →
22.2.1rc1 26 Jun 2026 H1 U3 Apache-2.0 Yes Details →
22.2.0 22 Jun 2026 H1 U3 Apache-2.0 Yes Details →
22.2.0rc1 19 Jun 2026 H1 U3 Apache-2.0 Yes Details →
22.1.0 07 Jun 2026 H1 U3 Apache-2.0 Yes Details →
22.1.0rc1 03 Jun 2026 H1 U3 Apache-2.0 Yes Details →
22.0.0 23 May 2026 H1 U3 Apache-2.0 Yes Details →
22.0.0rc1 19 May 2026 H2 U4 Apache-2.0 Yes Details →
21.3.0 11 May 2026 H2 U4 Apache-2.0 Yes Details →
21.3.0rc1 06 May 2026 H2 U4 Apache-2.0 Yes Details →
21.2.0 26 Apr 2026 H2 U4 Apache-2.0 Yes Details →
21.2.0rc1 22 Apr 2026 H2 U4 Apache-2.0 Yes Details →
21.1.0 12 Apr 2026 H2 U4 Apache-2.0 Yes Details →
21.1.0rc1 08 Apr 2026 H2 U4 Apache-2.0 Yes Details →
21.0.0 28 Mar 2026 H2 U4 Apache-2.0 Yes Details →
21.0.0rc2 24 Mar 2026 H2 U4 Apache-2.0 Yes Details →
21.0.0rc1 10 Mar 2026 H2 U4 Apache-2.0 Yes Details →
20.0.0 02 Mar 2026 H2 U4 Apache-2.0 Yes Details →
20.0.0rc2 26 Feb 2026 H2 U4 Apache-2.0 Yes Details →
20.0.0rc1 11 Feb 2026 H2 U4 Apache-2.0 Yes Details →
19.5.0 02 Feb 2026 H2 U4 Apache-2.0 Yes Details →
19.5.0rc1 28 Jan 2026 H2 U4 Apache-2.0 Yes Details →
19.4.0 21 Jan 2026 H2 U4 Apache-2.0 Yes Details →
19.4.0rc2 18 Jan 2026 H2 U4 Apache-2.0 Yes Details →
19.4.0rc1 13 Jan 2026 H2 U4 Apache-2.0 Yes Details →
19.3.0 02 Jan 2026 H2 U4 Apache-2.0 Yes Details →
19.3.0rc1 30 Dec 2025 H2 U4 Apache-2.0 Yes Details →
19.2.0 13 Dec 2025 H2 U4 Apache-2.0 Yes Details →
19.2.0rc1 09 Dec 2025 H2 U4 Apache-2.0 Yes Details →
19.1.0 02 Dec 2025 H2 U4 Apache-2.0 Yes Details →
19.1.0rc2 01 Dec 2025 H2 U4 Apache-2.0 Yes Details →
19.1.0rc1 27 Nov 2025 H2 U4 Apache-2.0 Yes Details →
19.0.0 17 Nov 2025 H2 U4 Apache-2.0 Yes Details →
19.0.0rc1 14 Nov 2025 H2 U4 Apache-2.0 Yes Details →
18.1.0 26 Oct 2025 H2 U4 non-standard Yes Details →
18.1.0rc1 22 Oct 2025 H2 U4 non-standard Yes Details →
18.0.0 22 Sep 2025 H2 U4 non-standard Yes Details →
18.0.0rc1 18 Sep 2025 H2 U4 non-standard Yes Details →
17.2.0 09 Sep 2025 H2 U4 non-standard Yes Details →
17.2.0rc1 05 Sep 2025 H2 U4 non-standard Yes Details →
17.1.0 11 Aug 2025 H2 U4 non-standard Yes Details →
17.1.0rc1 07 Aug 2025 H2 U4 non-standard Yes Details →
17.0.0 02 Aug 2025 H2 U4 non-standard Yes Details →
17.0.0rc1 29 Jul 2025 H2 U4 non-standard Yes Details →
16.1.0 06 Jul 2025 H2 U4 non-standard Yes Details →
16.1.0rc1 03 Jul 2025 H2 U4 non-standard Yes Details →
16.0.0 18 Jun 2025 H2 U4 non-standard Yes Details →
16.0.0rc1 15 Jun 2025 H2 U4 non-standard Yes Details →
15.1.0 19 Apr 2025 H2 U4 non-standard Yes Details →
15.1.0rc1 16 Apr 2025 H2 U4 non-standard Yes Details →
15.0.1 14 Apr 2025 H2 U4 non-standard Yes Details →
15.0.1rc1 10 Apr 2025 H2 U4 non-standard Yes Details →
15.0.0 09 Apr 2025 H2 U4 non-standard Yes Details →
15.0.0rc1 06 Apr 2025 H2 U4 non-standard Yes Details →
14.1.0 31 Mar 2025 H2 U4 non-standard Yes Details →
14.1.0rc1 26 Mar 2025 H2 U4 non-standard Yes Details →
14.0.0 26 Feb 2025 H2 U4 non-standard Yes Details →
14.0.0rc1 21 Feb 2025 H2 U4 non-standard Yes Details →
13.0.0 21 Feb 2025 H2 U4 non-standard Yes Details →
12.0.0 26 Dec 2024 H2 U4 non-standard Yes Details →
12.0.0rc2 22 Dec 2024 H2 U4 non-standard Yes Details →
12.0.0rc1 20 Dec 2024 H2 U4 non-standard Yes Details →
11.0.0 27 Nov 2024 H2 U4 non-standard Yes Details →
11.0.0rc1 24 Nov 2024 H2 U4 non-standard Yes Details →
10.26.0 18 Nov 2024 H2 U4 non-standard Yes Details →
10.26.0rc1 14 Nov 2024 H2 U4 non-standard Yes Details →
10.25.0 31 Oct 2024 H2 U4 non-standard Yes Details →
10.25.0rc1 27 Oct 2024 H2 U4 non-standard Yes Details →
10.24.0 14 Oct 2024 H2 U4 non-standard Yes Details →
10.24.0rc1 09 Oct 2024 H2 U4 non-standard Yes Details →
10.23.0 24 Sep 2024 H2 U4 non-standard Yes Details →
10.23.0rc1 21 Sep 2024 H2 U4 non-standard Yes Details →
10.22.0 22 Aug 2024 H2 U4 non-standard Yes Details →
10.22.0rc1 19 Aug 2024 H2 U4 non-standard Yes Details →
10.21.1 06 Aug 2024 H2 U4 non-standard Yes Details →
10.21.1rc2 03 Aug 2024 H2 U4 non-standard Yes Details →
10.21.1rc1 28 Jul 2024 H2 U4 non-standard Yes Details →
10.21.0 12 Jul 2024 H2 U4 non-standard Yes Details →
10.21.0rc1 09 Jul 2024 H2 U4 non-standard Yes Details →
10.20.0 27 Jun 2024 H2 U4 non-standard Yes Details →
10.20.0rc1 22 Jun 2024 H2 U4 non-standard Yes Details →
10.19.0 30 May 2024 H2 U4 non-standard Yes Details →
10.19.0rc1 26 May 2024 H2 U4 non-standard Yes Details →
10.18.0 17 May 2024 H2 U4 — Yes Details →
10.18.0rc2 12 May 2024 H2 U4 — Yes Details →
10.18.0rc1 01 May 2024 H2 U4 — Yes Details →
10.17.0 13 Apr 2024 H2 U4 — Yes Details →
10.17.0rc1 10 Apr 2024 H2 U4 — Yes Details →
10.16.0 08 Mar 2024 H2 U4 — Yes Details →
10.16.0rc1 04 Mar 2024 H2 U4 — Yes Details →
10.15.0 15 Feb 2024 H2 U4 — Yes Details →
10.15.0rc1 12 Feb 2024 H2 U4 — Yes Details →
10.14.0 27 Jan 2024 H2 U4 — Yes Details →
10.14.0rc2 26 Jan 2024 H2 U4 — Yes Details →
10.14.0rc1 22 Jan 2024 H2 U4 — Yes Details →
10.13.1 31 Dec 2023 H2 U4 — Yes Details →
10.13.1rc1 28 Dec 2023 H2 U4 — Yes Details →
10.13.0 27 Dec 2023 H2 U4 — Yes Details →
10.13.0rc3 23 Dec 2023 H2 U4 — Yes Details →
10.13.0rc2 12 Dec 2023 H2 U4 — Yes Details →
10.13.0rc1 07 Dec 2023 H2 U4 — Yes Details →
10.12.0 29 Nov 2023 H2 U4 — Yes Details →
10.12.0rc1 24 Nov 2023 H2 U4 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2
  • 2026 8

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

03 Vulnerabilities

Recorded vulnerabilities for apache-airflow-providers-google

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-25691: Apache Airflow Google Provider Improper Input Validation vulnerability 9.8 critical 8.10.0 24 Feb 2023
CVE-2023-25691: Apache Airflow Google Provider Improper Input Validation Vulnerability 9.8 critical 8.10.0 29 Jun 2026
CVE-2026-45361: Apache Airflow Providers-Google SSH Host-Key Verification Disabled 8.1 high 22.0.0 25 May 2026
CVE-2026-45361: Apache Airflow providers-google's ComputeEngineSSHHook Disables SSH Host-Key Verification by Default 8.1 high 22.0.0 26 May 2026
CVE-2026-49297: Apache Airflow Google Provider Package Vulnerability Allows Arbitrary File Overwrite 8.1 high 22.2.1 06 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: 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 apache-airflow-providers-google

Is apache-airflow-providers-google safe to use?

Vulert records 10 vulnerabilities for apache-airflow-providers-google in PyPI: 1 critical, 3 high, 0 medium and 0 low, plus 6 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 apache-airflow-providers-google's Vulert package health score?

Vulert scores apache-airflow-providers-google 63/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 apache-airflow-providers-google affected?

No. 22.7.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 apache-airflow-providers-google should I use?

22.7.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 apache-airflow-providers-google have?

10 vulnerabilities are recorded for apache-airflow-providers-google in the PyPI ecosystem: 1 critical, 3 high, 0 medium and 0 low, plus 6 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 apache-airflow-providers-google vulnerabilities disclosed?

8 vulnerabilities were recorded for apache-airflow-providers-google in the last 12 months, and the oldest entry in this database dates to 24 Feb 2023. 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 apache-airflow-providers-google 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 apache-airflow-providers-google for upcoming vulnerabilities?

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