VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

celery: vulnerability history, versions and safety

celery is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 77 releases, from Dec 2011 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M1 U2
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 celery vulnerabilities

Vulert verdict on celery 5.6.3 i

Updated on 23 Oct 2026

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

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

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

  • Current release 5.6.3 — unaffected i
  • Vulnerabilities on record 4 over 10 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 2,034 packages i
  • Stars 29,017 i
  • OpenSSF scorecard 5/10 i
  • Last release 6 months ago i
  • Licence BSD-3-Clause 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 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
5.7.0rc1 18 Oct 2026 none BSD-3-Clause — Details →
5.7.0b1 06 Oct 2026 none BSD-3-Clause — Details →
5.7.0a1 22 Sep 2026 none BSD-3-Clause — Details →
5.6.3 26 Mar 2026 none BSD-3-Clause — Details →
5.6.2 04 Jan 2026 none BSD-3-Clause — Details →
5.6.1 29 Dec 2025 none BSD-3-Clause — Details →
5.6.0 30 Nov 2025 none BSD-3-Clause — Details →
5.6.0rc2 22 Nov 2025 none BSD-3-Clause — Details →
5.6.0rc1 01 Nov 2025 none BSD-3-Clause — Details →
5.6.0b2 20 Oct 2025 none BSD-3-Clause — Details →
5.6.0b1 15 Sep 2025 none BSD-3-Clause — Details →
5.5.3 01 Jun 2025 none BSD-3-Clause — Details →
5.5.2 25 Apr 2025 none BSD-3-Clause — Details →
5.5.1 07 Apr 2025 none BSD-3-Clause — Details →
5.5.0 31 Mar 2025 none BSD-3-Clause — Details →
5.5.0rc5 25 Feb 2025 none BSD-3-Clause — Details →
5.5.0rc4 19 Dec 2024 none BSD-3-Clause — Details →
5.5.0rc3 03 Dec 2024 none BSD-3-Clause — Details →
5.5.0rc2 18 Nov 2024 none BSD-3-Clause — Details →
5.5.0rc1 08 Oct 2024 none BSD-3-Clause — Details →
5.5.0b4 30 Sep 2024 none BSD-3-Clause — Details →
5.5.0b3 08 Sep 2024 none BSD-3-Clause — Details →
5.5.0b2 06 Aug 2024 none BSD-3-Clause — Details →
5.5.0b1 24 Jul 2024 none BSD-3-Clause — Details →
5.4.0 17 Apr 2024 none BSD-3-Clause — Details →
5.4.0rc2 27 Mar 2024 none BSD-3-Clause — Details →
5.4.0rc1 17 Jan 2024 none BSD-3-Clause — Details →
5.3.6 22 Nov 2023 none BSD-3-Clause — Details →
5.3.5 10 Nov 2023 none BSD-3-Clause — Details →
5.3.4 03 Sep 2023 none BSD-3-Clause — Details →
5.3.1 18 Jun 2023 none BSD-3-Clause — Details →
5.3.0 06 Jun 2023 none BSD-3-Clause — Details →
5.3.0rc2 31 May 2023 none BSD-3-Clause — Details →
5.3.0rc1 11 May 2023 none BSD-3-Clause — Details →
5.3.0b2 19 Feb 2023 none BSD-3-Clause — Details →
5.3.0b1 01 Aug 2022 none non-standard — Details →
5.3.0a1 29 Jun 2022 none non-standard — Details →
5.2.7 29 May 2022 none non-standard — Details →
5.2.6 05 Apr 2022 none non-standard — Details →
5.2.5 03 Apr 2022 none non-standard — Details →
5.2.4 03 Apr 2022 none non-standard — Details →
5.2.3 29 Dec 2021 none non-standard — Details →
5.2.2 26 Dec 2021 none non-standard — Details →
5.2.1 16 Nov 2021 H1 U1 non-standard Yes Details →
5.2.0 08 Nov 2021 H1 U1 non-standard Yes Details →
5.2.0rc2 02 Nov 2021 H1 U1 non-standard Yes Details →
5.2.0rc1 26 Sep 2021 H1 U1 non-standard Yes Details →
5.2.0b3 02 Sep 2021 H1 U1 non-standard Yes Details →
5.2.0b2 17 Aug 2021 H1 U1 non-standard Yes Details →
5.2.0b1 11 Aug 2021 H1 U1 non-standard Yes Details →
5.1.2 28 Jun 2021 H1 U1 non-standard Yes Details →
5.0.6 28 Jun 2021 H1 U1 non-standard Yes Details →
5.1.1 17 Jun 2021 H1 U1 non-standard Yes Details →
5.1.0 23 May 2021 H1 U1 non-standard Yes Details →
5.1.0rc1 19 May 2021 H1 U1 non-standard Yes Details →
5.1.0b2 02 May 2021 H1 U1 non-standard Yes Details →
5.1.0b1 02 Apr 2021 H1 U1 non-standard Yes Details →
5.0.5 16 Dec 2020 H1 U1 non-standard Yes Details →
5.0.4 08 Dec 2020 H1 U1 non-standard Yes Details →
5.0.3 03 Dec 2020 H1 U1 non-standard Yes Details →
5.0.2 02 Nov 2020 H1 U1 non-standard Yes Details →
5.0.1 18 Oct 2020 H1 U1 non-standard Yes Details →
5.0.0 24 Sep 2020 H1 U1 non-standard Yes Details →
4.3.1 10 Sep 2020 H1 U1 non-standard Yes Details →
5.0.0rc3 07 Sep 2020 H1 U1 non-standard Yes Details →
5.0.0rc2 01 Sep 2020 H1 U1 non-standard Yes Details →
5.0.0rc1 24 Aug 2020 H1 U1 non-standard Yes Details →
5.0.0b1 19 Aug 2020 H1 U1 non-standard Yes Details →
5.0.0a2 05 Aug 2020 H1 U1 non-standard Yes Details →
5.0.0a1 02 Aug 2020 H1 U1 non-standard Yes Details →
4.4.7 31 Jul 2020 H1 U1 non-standard Yes Details →
4.4.6 24 Jun 2020 H1 U1 non-standard Yes Details →
4.4.5 08 Jun 2020 H1 U1 non-standard Yes Details →
4.4.4 03 Jun 2020 H1 U1 non-standard Yes Details →
4.4.3 01 Jun 2020 H1 U1 non-standard Yes Details →
4.4.2 17 Mar 2020 H1 U1 non-standard Yes Details →
4.4.1 02 Mar 2020 H1 U1 non-standard Yes Details →
4.4.0 16 Dec 2019 H1 U1 non-standard Yes Details →
4.4.0rc5 07 Dec 2019 H1 U1 non-standard Yes Details →
4.4.0rc4 10 Nov 2019 H1 U1 non-standard Yes Details →
4.4.0rc3 14 Aug 2019 H1 U1 non-standard Yes Details →
4.4.0rc2 14 Jun 2019 H1 U1 non-standard Yes Details →
4.4.0rc1 06 Jun 2019 H1 U1 non-standard Yes Details →
4.3.0 31 Mar 2019 H1 U1 non-standard Yes Details →
4.3.0rc3 21 Mar 2019 H1 U1 non-standard Yes Details →
4.2.2 20 Mar 2019 H1 U1 non-standard Yes Details →
4.3.0rc2 03 Mar 2019 H1 U1 non-standard Yes Details →
4.3.0rc1 20 Feb 2019 H1 U1 non-standard Yes Details →
4.2.1 18 Jul 2018 H1 U1 non-standard Yes Details →
4.2.0 10 Jun 2018 H1 U1 non-standard Yes Details →
4.2.0rc4 22 May 2018 H1 U1 non-standard Yes Details →
4.1.1 21 May 2018 H1 U1 non-standard Yes Details →
4.2.0rc3 29 Apr 2018 H1 U1 non-standard Yes Details →
4.2.0rc2 02 Apr 2018 H1 U1 non-standard Yes Details →
3.1.26.post2 24 Mar 2018 H1 U1 non-standard Yes Details →
3.1.26.post1 24 Mar 2018 H1 U1 non-standard Yes Details →
4.2.0rc1 23 Mar 2018 H1 U1 non-standard Yes Details →
4.1.0 24 Jul 2017 H1 U1 non-standard Yes Details →
4.0.2 16 Dec 2016 H1 U1 non-standard Yes Details →
4.0.1 09 Dec 2016 H1 U1 non-standard Yes Details →
3.1.25 05 Nov 2016 H1 U1 — Yes Details →
4.0.0 04 Nov 2016 H1 U1 — Yes Details →
4.0.0rc7 03 Nov 2016 H1 U1 — Yes Details →
4.0.0rc6 22 Oct 2016 H1 U1 — Yes Details →
4.0.0rc5 15 Oct 2016 H1 U1 — Yes Details →
3.1.24 01 Oct 2016 H1 U1 — Yes Details →
4.0.0rc4 08 Sep 2016 H1 U1 — Yes Details →
4.0.0rc3 08 Jul 2016 H1 U1 — Yes Details →
3.1.23 10 Mar 2016 H1 U1 — Yes Details →
3.1.22 08 Mar 2016 H1 U1 — Yes Details →
3.1.21 04 Mar 2016 H1 U1 — Yes Details →
3.1.20 23 Jan 2016 H1 U1 — Yes Details →
3.1.19 26 Oct 2015 H1 U1 — Yes Details →
3.1.18 22 Apr 2015 H1 U1 — Yes Details →
3.1.17 19 Nov 2014 H1 U1 — Yes Details →
3.1.16 03 Oct 2014 H1 U1 — Yes Details →
3.1.15 14 Sep 2014 H1 U1 — Yes Details →
3.1.14 08 Sep 2014 H1 U1 — Yes Details →
3.1.13 10 Jul 2014 H1 U1 — Yes Details →
3.0.25 10 Jul 2014 H1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2011 1
  • 2021 1
  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for celery

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-23727: OS Command Injection in celery 7.5 high 5.2.2 06 Jan 2022
CVE-2011-4356: Privilege Escalation in Celery N/A unrated 2.2.8 05 Dec 2011
CVE-2021-23727: Command Injection Vulnerability in Celery N/A unrated 5.2.2 29 Dec 2021
CVE-2011-4356: Celery local privilege escalation vulnerability N/A medium 2.2.8 17 May 2022

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 celery

Is celery safe to use?

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

Vulert scores celery 84/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 celery affected?

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

5.6.3 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 celery have?

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

0 vulnerabilities were recorded for celery in the last 12 months, and the oldest entry in this database dates to 05 Dec 2011. 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 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 celery for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the 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.