Vulnerability Database · PyPI · Package report

apache-airflow: vulnerability history, versions and safety

apache-airflow is a package in the PyPI ecosystem. Vulert records 304 vulnerabilities for it across 120 releases, from Aug 2018 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
304 vulnerabilities recorded C13 H45 M82 L5 U159
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
135 in the last 12 months

Most recent disclosure 21 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on apache-airflow 3.3.2 i

Updated on 22 Oct 2026

Careful: 3.3.2 has 6 known vulnerabilities, and 5 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 3.3.2 — affected i
  • Vulnerabilities on record 304 over 8 years · 135 in the last year i
  • Latest disclosure 21 Sep 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 5 i
  • Depended on by 469 packages i
  • Stars 47,242 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month 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 apache-airflow, 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
3.4.0b2 20 Oct 2026 M1 U5 Apache-2.0 No Details →
3.4.0b1 13 Oct 2026 M1 U5 Apache-2.0 No Details →
3.3.2 17 Sep 2026 M1 U5 Apache-2.0 No Details →
3.3.2rc1 13 Sep 2026 U2 Apache-2.0 Yes Details →
3.3.1 12 Aug 2026 U3 Apache-2.0 No Details →
3.3.1rc2 11 Aug 2026 H4 M8 U14 Apache-2.0 Yes Details →
3.3.1rc1 07 Aug 2026 H4 M8 U14 Apache-2.0 Yes Details →
3.3.0 06 Jul 2026 H4 M8 U15 Apache-2.0 No Details →
3.3.0rc2 03 Jul 2026 C1 H1 M12 U17 Apache-2.0 No Details →
3.3.0rc1 30 Jun 2026 C1 H1 M12 U17 Apache-2.0 No Details →
3.3.0b2 24 Jun 2026 C1 H1 M12 U17 Apache-2.0 No Details →
3.3.0b1 17 Jun 2026 C1 H1 M12 U17 Apache-2.0 No Details →
3.2.2 29 May 2026 C1 H1 M12 U17 Apache-2.0 No Details →
3.2.2rc3 27 May 2026 C2 H5 M21 L2 U33 Apache-2.0 No Details →
3.2.2rc2 26 May 2026 C2 H5 M21 L2 U33 Apache-2.0 No Details →
3.2.2rc1 21 May 2026 C2 H5 M21 L2 U33 Apache-2.0 No Details →
3.2.1 22 Apr 2026 C2 H5 M21 L2 U37 Apache-2.0 No Details →
3.2.1rc3 21 Apr 2026 C2 H5 M21 L2 U37 Apache-2.0 No Details →
3.2.1rc2 17 Apr 2026 C2 H5 M21 L2 U37 Apache-2.0 No Details →
3.2.1rc1 15 Apr 2026 C2 H5 M21 L2 U37 Apache-2.0 No Details →
3.2.0 07 Apr 2026 C2 H5 M23 L2 U39 Apache-2.0 No Details →
3.2.0rc2 03 Apr 2026 C3 H5 M25 L2 U45 Apache-2.0 No Details →
3.2.0rc1 30 Mar 2026 C3 H5 M25 L2 U45 Apache-2.0 No Details →
3.2.0b2 23 Mar 2026 C3 H5 M25 L2 U45 Apache-2.0 No Details →
2.11.2 14 Mar 2026 C1 H4 M23 U37 non-standard No Details →
3.1.8 11 Mar 2026 C3 H5 M25 L2 U45 Apache-2.0 No Details →
3.1.8rc2 10 Mar 2026 C3 H7 M27 L2 U49 Apache-2.0 No Details →
2.11.2rc1 09 Mar 2026 C1 H4 M23 U37 non-standard No Details →
3.1.8rc1 06 Mar 2026 C3 H7 M27 L2 U49 Apache-2.0 No Details →
3.2.0b1 03 Mar 2026 C3 H5 M25 L2 U45 Apache-2.0 No Details →
2.11.1rc2 16 Feb 2026 C1 H5 M25 U40 non-standard No Details →
2.11.1 16 Feb 2026 C1 H4 M23 U37 non-standard No Details →
2.11.1rc1 16 Feb 2026 C1 H5 M25 U40 non-standard No Details →
3.1.7 04 Feb 2026 C3 H7 M28 L2 U49 Apache-2.0 No Details →
3.1.7rc2 03 Feb 2026 C3 H7 M29 L2 U51 Apache-2.0 No Details →
3.1.7rc1 30 Jan 2026 C3 H7 M29 L2 U51 Apache-2.0 No Details →
3.1.6 13 Jan 2026 C3 H7 M29 L2 U51 Apache-2.0 No Details →
3.1.6rc1 08 Jan 2026 C3 H9 M29 L2 U53 Apache-2.0 No Details →
3.1.5 12 Dec 2025 C3 H9 M29 L2 U53 Apache-2.0 No Details →
3.1.5rc1 12 Dec 2025 C3 H9 M30 L2 U53 Apache-2.0 No Details →
3.1.4 10 Dec 2025 C3 H9 M30 L2 U54 Apache-2.0 No Details →
3.1.4rc2 08 Dec 2025 C3 H9 M30 L2 U55 Apache-2.0 No Details →
3.1.4rc1 04 Dec 2025 C3 H9 M30 L2 U55 Apache-2.0 No Details →
3.1.3 14 Nov 2025 C3 H9 M30 L2 U55 Apache-2.0 No Details →
3.1.3rc1 11 Nov 2025 C3 H9 M30 L2 U55 Apache-2.0 No Details →
3.1.2 05 Nov 2025 C3 H9 M30 L2 U55 non-standard No Details →
3.1.2rc2 04 Nov 2025 C3 H9 M30 L2 U55 non-standard No Details →
3.1.2rc1 31 Oct 2025 C3 H9 M30 L2 U55 non-standard No Details →
3.1.1 27 Oct 2025 C3 H9 M30 L2 U55 non-standard No Details →
3.1.1rc2 23 Oct 2025 C3 H9 M32 L2 U58 non-standard No Details →
3.1.1rc1 22 Oct 2025 C3 H9 M32 L2 U58 non-standard No Details →
3.1.0 25 Sep 2025 C3 H9 M32 L2 U58 non-standard No Details →
3.1.0rc2 23 Sep 2025 C3 H8 M30 L2 U54 non-standard No Details →
3.1.0rc1 19 Sep 2025 C3 H8 M30 L2 U54 non-standard No Details →
3.1.0b2 15 Sep 2025 C3 H8 M30 L2 U54 non-standard No Details →
3.1.0b1 09 Sep 2025 C3 H8 M30 L2 U54 non-standard No Details →
3.0.6 29 Aug 2025 C3 H8 M30 L2 U54 non-standard No Details →
3.0.6rc2 26 Aug 2025 C3 H8 M30 L2 U54 non-standard No Details →
3.0.6rc1 22 Aug 2025 C3 H8 M30 L2 U54 non-standard No Details →
3.0.5 20 Aug 2025 C3 H8 M30 L2 U54 non-standard No Details →
3.0.5rc3 18 Aug 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.5rc2 14 Aug 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.5rc1 13 Aug 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.4 08 Aug 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.4rc2 06 Aug 2025 C3 H8 M32 L2 U55 non-standard No Details →
3.0.4rc1 04 Aug 2025 C3 H8 M32 L2 U55 non-standard No Details →
3.0.3 14 Jul 2025 C3 H8 M32 L2 U55 non-standard No Details →
3.0.3rc6 11 Jul 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.3rc5 09 Jul 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.3rc4 07 Jul 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.3rc3 04 Jul 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.3rc2 03 Jul 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.3rc1 02 Jul 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.2 10 Jun 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.2rc2 06 Jun 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.2rc1 03 Jun 2025 C3 H8 M31 L2 U55 non-standard No Details →
2.11.0 20 May 2025 C1 H6 M26 U40 non-standard No Details →
2.11.0rc1 15 May 2025 C1 H6 M26 U40 non-standard No Details →
3.0.1 12 May 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.1rc1 06 May 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.0 22 Apr 2025 C3 H8 M31 L2 U55 non-standard No Details →
3.0.0rc4 19 Apr 2025 C1 H5 M24 U38 non-standard No Details →
3.0.0rc3 16 Apr 2025 C1 H5 M24 U38 non-standard No Details →
3.0.0rc2 10 Apr 2025 C1 H5 M24 U38 non-standard No Details →
3.0.0rc1.post4 03 Apr 2025 C1 H5 M24 U38 non-standard No Details →
3.0.0rc1.post3 03 Apr 2025 C1 H5 M24 U38 non-standard No Details →
3.0.0rc1.post2 03 Apr 2025 C1 H5 M24 U38 non-standard No Details →
3.0.0rc1.post1 03 Apr 2025 C1 H5 M24 U38 non-standard No Details →
3.0.0rc1 03 Apr 2025 C1 H5 M24 U38 non-standard No Details →
3.0.0b4 20 Mar 2025 C1 H5 M24 U38 non-standard No Details →
2.10.5 10 Feb 2025 C1 H6 M26 U40 non-standard No Details →
2.10.5rc1 05 Feb 2025 C1 H6 M26 U40 non-standard No Details →
2.10.4 16 Dec 2024 C1 H6 M26 U40 non-standard No Details →
2.10.4rc1 10 Dec 2024 C1 H6 M26 U40 non-standard No Details →
2.10.3 05 Nov 2024 C1 H6 M26 U40 non-standard No Details →
2.10.3rc2 01 Nov 2024 C1 H6 M26 L1 U42 non-standard No Details →
2.10.3rc1 28 Oct 2024 C1 H6 M26 L1 U42 non-standard No Details →
2.10.2 20 Sep 2024 C1 H6 M26 L1 U42 non-standard No Details →
2.10.2rc1 17 Sep 2024 C1 H6 M26 L1 U42 non-standard No Details →
2.10.1 06 Sep 2024 C1 H6 M26 L1 U42 non-standard No Details →
2.10.1rc1 02 Sep 2024 C1 H8 M26 L1 U43 — No Details →
2.10.0 15 Aug 2024 C1 H8 M26 L1 U43 — No Details →
2.10.0rc1 12 Aug 2024 C1 H7 M27 L1 U44 — No Details →
2.10.0b2 01 Aug 2024 C1 H7 M27 L1 U44 — No Details →
2.10.0b1 25 Jul 2024 C1 H7 M27 L1 U44 — No Details →
2.9.3 16 Jul 2024 C1 H7 M27 L1 U44 — No Details →
2.9.3rc1 12 Jul 2024 C1 H8 M28 L1 U46 — No Details →
2.9.2 10 Jun 2024 C1 H8 M28 L1 U46 — No Details →
2.9.2rc1 06 Jun 2024 C1 H8 M28 L2 U47 — No Details →
2.9.1 06 May 2024 C1 H8 M28 L2 U47 — No Details →
2.9.1rc2 02 May 2024 C1 H8 M29 L2 U47 — No Details →
2.9.1rc1 30 Apr 2024 C1 H8 M29 L2 U47 — No Details →
2.9.0 08 Apr 2024 C1 H8 M29 L2 U47 — No Details →
2.9.0rc3 07 Apr 2024 C1 H8 M29 L2 U48 — No Details →
2.9.0rc2 04 Apr 2024 C1 H8 M29 L2 U48 — No Details →
2.9.0rc1 03 Apr 2024 C1 H8 M29 L2 U48 — No Details →
2.9.0b2 27 Mar 2024 C1 H8 M29 L2 U48 — No Details →
2.8.4 25 Mar 2024 C1 H8 M29 L2 U48 — No Details →
2.9.0b1 21 Mar 2024 C1 H8 M29 L2 U48 — No Details →
2.8.4rc1 20 Mar 2024 C1 H8 M30 L2 U49 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2019 15
  • 2020 21
  • 2021 13
  • 2022 33
  • 2023 54
  • 2024 30
  • 2025 8
  • 2026 129

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

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 apache-airflow

Is apache-airflow safe to use?

Vulert records 304 vulnerabilities for apache-airflow in PyPI: 13 critical, 45 high, 82 medium and 5 low, plus 159 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is apache-airflow's Vulert package health score?

Vulert scores apache-airflow 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of apache-airflow affected?

Yes. 3.3.2, the version you would install today, has 6 known vulnerabilities, and 5 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of apache-airflow should I use?

3.3.2 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 have?

304 vulnerabilities are recorded for apache-airflow in the PyPI ecosystem: 13 critical, 45 high, 82 medium and 5 low, plus 159 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 vulnerabilities disclosed?

135 vulnerabilities were recorded for apache-airflow in the last 12 months, and the oldest entry in this database dates to 06 Aug 2018. 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 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 for upcoming vulnerabilities?

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