Vulnerability Database · PyPI · Package report

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

apache-airflow-providers-celery is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 9 releases, from Oct 2023 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
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on apache-airflow-providers-celery 3.25.0 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 3.25.0 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 15 packages 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 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-providers-celery, 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.26.0rc1 21 Oct 2026 none Apache-2.0 — Details →
3.25.0 13 Oct 2026 none Apache-2.0 — Details →
3.25.0rc1 08 Oct 2026 none Apache-2.0 — Details →
3.24.1 29 Sep 2026 none Apache-2.0 — Details →
3.24.1rc1 24 Sep 2026 none Apache-2.0 — Details →
3.24.0 14 Sep 2026 none Apache-2.0 — Details →
3.24.0rc1 10 Sep 2026 none Apache-2.0 — Details →
3.23.1 08 Aug 2026 none Apache-2.0 — Details →
3.23.1rc2 06 Aug 2026 none Apache-2.0 — Details →
3.23.1rc1 03 Aug 2026 none Apache-2.0 — Details →
3.23.0 28 Jul 2026 none Apache-2.0 — Details →
3.23.0rc1 23 Jul 2026 none Apache-2.0 — Details →
3.22.0 10 Jul 2026 none Apache-2.0 — Details →
3.22.0rc1 07 Jul 2026 none Apache-2.0 — Details →
3.21.0 03 Jul 2026 none Apache-2.0 — Details →
3.21.0rc1 26 Jun 2026 none Apache-2.0 — Details →
3.20.0 23 May 2026 none Apache-2.0 — Details →
3.20.0rc1 19 May 2026 none Apache-2.0 — Details →
3.19.0 01 May 2026 none Apache-2.0 — Details →
3.19.0rc2 27 Apr 2026 none Apache-2.0 — Details →
3.19.0rc1 22 Apr 2026 none Apache-2.0 — Details →
3.18.0 12 Apr 2026 none Apache-2.0 — Details →
3.18.0rc1 08 Apr 2026 none Apache-2.0 — Details →
3.17.2 28 Mar 2026 none Apache-2.0 — Details →
3.17.2rc1 24 Mar 2026 none Apache-2.0 — Details →
3.17.1 13 Mar 2026 none Apache-2.0 — Details →
3.17.1rc1 10 Mar 2026 none Apache-2.0 — Details →
3.17.0 04 Mar 2026 none Apache-2.0 — Details →
3.17.0rc2 03 Mar 2026 none Apache-2.0 — Details →
3.17.0rc1 26 Feb 2026 none Apache-2.0 — Details →
3.16.0 14 Feb 2026 none Apache-2.0 — Details →
3.16.0rc1 11 Feb 2026 none Apache-2.0 — Details →
3.15.2 02 Feb 2026 none Apache-2.0 — Details →
3.15.2rc1 28 Jan 2026 none Apache-2.0 — Details →
3.15.1 17 Jan 2026 none Apache-2.0 — Details →
3.15.1rc1 13 Jan 2026 none Apache-2.0 — Details →
3.15.0 02 Jan 2026 none Apache-2.0 — Details →
3.15.0rc1 30 Dec 2025 none Apache-2.0 — Details →
3.14.1 13 Dec 2025 none Apache-2.0 — Details →
3.14.1rc1 09 Dec 2025 none Apache-2.0 — Details →
3.14.0 02 Dec 2025 none Apache-2.0 — Details →
3.14.0rc2 01 Dec 2025 none Apache-2.0 — Details →
3.14.0rc1 27 Nov 2025 none Apache-2.0 — Details →
3.13.1 17 Nov 2025 none Apache-2.0 — Details →
3.13.1rc1 14 Nov 2025 none Apache-2.0 — Details →
3.13.0 26 Oct 2025 none non-standard — Details →
3.13.0rc1 22 Oct 2025 none non-standard — Details →
3.12.4 28 Sep 2025 none non-standard — Details →
3.12.4rc1 25 Sep 2025 none non-standard — Details →
3.12.3 09 Sep 2025 none non-standard — Details →
3.12.3rc1 05 Sep 2025 none non-standard — Details →
3.12.2 02 Aug 2025 none non-standard — Details →
3.12.2rc1 29 Jul 2025 none non-standard — Details →
3.12.1 06 Jul 2025 none non-standard — Details →
3.12.1rc1 03 Jul 2025 none non-standard — Details →
3.12.0 18 Jun 2025 none non-standard — Details →
3.12.0rc1 15 Jun 2025 none non-standard — Details →
3.11.0 18 May 2025 none non-standard — Details →
3.11.0rc1 14 May 2025 none non-standard — Details →
3.10.6 14 Apr 2025 none non-standard — Details →
3.10.6rc1 10 Apr 2025 none non-standard — Details →
3.10.5 09 Apr 2025 none non-standard — Details →
3.10.5rc1 06 Apr 2025 none non-standard — Details →
3.10.4 31 Mar 2025 none non-standard — Details →
3.10.4rc1 26 Mar 2025 none non-standard — Details →
3.10.4b1 20 Mar 2025 none non-standard — Details →
3.10.3 13 Mar 2025 none non-standard — Details →
3.10.3rc1 09 Mar 2025 none non-standard — Details →
3.10.2 26 Feb 2025 none non-standard — Details →
3.10.2rc1 21 Feb 2025 none non-standard — Details →
3.10.1 21 Feb 2025 none non-standard — Details →
3.10.0 27 Jan 2025 none non-standard — Details →
3.10.0rc2 26 Jan 2025 none non-standard — Details →
3.10.0rc1 23 Jan 2025 none non-standard — Details →
3.9.0 26 Dec 2024 none non-standard — Details →
3.9.0rc2 22 Dec 2024 none non-standard — Details →
3.9.0rc1 20 Dec 2024 none non-standard — Details →
3.8.5 27 Nov 2024 none non-standard — Details →
3.8.5rc1 24 Nov 2024 none non-standard — Details →
3.8.4 18 Nov 2024 none non-standard — Details →
3.8.4rc1 14 Nov 2024 none non-standard — Details →
3.8.3 14 Oct 2024 none non-standard — Details →
3.8.3rc1 09 Oct 2024 none non-standard — Details →
3.8.2 24 Sep 2024 none non-standard — Details →
3.8.2rc1 21 Sep 2024 none non-standard — Details →
3.8.1 28 Aug 2024 none non-standard — Details →
3.8.1rc1 25 Aug 2024 none non-standard — Details →
3.8.0 22 Aug 2024 none non-standard — Details →
3.8.0rc1 19 Aug 2024 none non-standard — Details →
3.7.3 06 Aug 2024 none non-standard — Details →
3.7.3rc1 03 Aug 2024 none non-standard — Details →
3.7.2 09 Jun 2024 none non-standard — Details →
3.7.2rc1 07 Jun 2024 none non-standard — Details →
3.7.1 30 May 2024 none non-standard — Details →
3.7.1rc1 26 May 2024 none non-standard — Details →
3.7.0 06 May 2024 none non-standard — Details →
3.7.0rc1 01 May 2024 none non-standard — Details →
3.6.2 13 Apr 2024 none non-standard — Details →
3.6.2rc1 10 Apr 2024 none non-standard — Details →
3.6.1 08 Mar 2024 none non-standard — Details →
3.6.1rc1 04 Mar 2024 none — — Details →
3.6.0 15 Feb 2024 none — — Details →
3.6.0rc1 12 Feb 2024 none — — Details →
3.5.2 27 Jan 2024 none — — Details →
3.5.2rc2 26 Jan 2024 none — — Details →
3.5.2rc1 22 Jan 2024 none — — Details →
3.5.1 27 Dec 2023 none — — Details →
3.5.1rc1 23 Dec 2023 none — — Details →
3.5.0 12 Dec 2023 none — — Details →
3.5.0rc1 07 Dec 2023 none — — Details →
3.4.1 21 Oct 2023 none — — Details →
3.4.1rc1 18 Oct 2023 H1 U1 — Yes Details →
3.4.0 17 Oct 2023 H1 U1 — Yes Details →
3.4.0rc1 13 Oct 2023 H1 U1 — Yes Details →
3.3.4 12 Sep 2023 H1 U1 — Yes Details →
3.3.4rc1 08 Sep 2023 H1 U1 — Yes Details →
3.3.3 29 Aug 2023 H1 U1 — Yes Details →
3.3.3rc1 25 Aug 2023 H1 U1 — Yes Details →
3.3.2 14 Aug 2023 H1 U1 — Yes Details →
3.3.2rc1 11 Aug 2023 H1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for apache-airflow-providers-celery

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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-celery

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

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

Vulert scores apache-airflow-providers-celery 82/100, which reads as in good shape. 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-celery affected?

No. 3.25.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-celery should I use?

3.25.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-celery have?

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

1 vulnerability was recorded for apache-airflow-providers-celery in the last 12 months, and the oldest entry in this database dates to 28 Oct 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-celery 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-celery for upcoming vulnerabilities?

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