Celery 3 lifecycle
Current status
Celery 3 is currently in standard support.
Security: 2 tracked advisories affecting this line. Details below — lifecycle and vulnerability status are separate.
Official lifecycle source: Celery PyPI releases
- Support phase
- standard support
- End of life
- Not officially published
- Latest release
- 3.0.9
- Released
- 31 Aug 2012
At a glance
- Version line
- 3
- Initial release
- 7 Jul 2012
- Lifecycle phase
- standard support
- Latest stable
- 3.0.9
- Latest release date
- 31 Aug 2012
- EOL
- Not officially published
- Risk
- low
- Releases tracked
- 54
Lifecycle timeline
Phases from published LifecyclePeriod records. Missing phases are not inferred.
Release
7 Jul 2012
standard supportcurrent
7 Jul 2012 → —
Source: Celery PyPI releases
Celery 3 is currently in standard support.
Upgrade options
Newer supported Celery version lines from CompatHub lifecycle data. Compatibility and security context use existing evidence only.
You are on Celery 3
Supported
Supported upgrade options
- Celery 5Upgrade planner →Supported· 2 major versions newer
- Celery 4Upgrade planner →Supported· 1 major version newer
Security
Advisories affecting Celery 3 (OSV.dev evidence). Known exploited status, due dates, and ransomware use from CISA KEV when matched.
- Known vulnerabilities
- 2
- Known exploited
- 0
- Highest CVSS
- —
- CVE-2021-23727GHSA-q4xr-rc97-m4xx
OS Command Injection in celery
- Affected:
- <5.2.2
- Fixed in:
- 5.2.2
- Source:
- OSV source · Advisory
- CVE-2021-23727PYSEC-2021-858
- Affected:
- <5.2.2
- Fixed in:
- 5.2.2
- Source:
- OSV source · Advisory
Latest release
Previous releases
3.0.10
20 Sept 2012
3.0.11
26 Sept 2012
3.0.8
29 Aug 2012
Release history
54 concrete releases tracked for this line.
| Version | Release date | Channel | Source |
|---|---|---|---|
| 3.0.9 | 31 Aug 2012 | stable | Source |
| 3.0.10 | 20 Sept 2012 | stable | Source |
| 3.0.11 | 26 Sept 2012 | stable | Source |
| 3.0.12 | 6 Nov 2012 | stable | Source |
| 3.0.13 | 7 Jan 2013 | stable | Source |
| 3.0.0 | 7 Jul 2012 | stable | Source |
| 3.0.1 | 10 Jul 2012 | stable | Source |
| 3.0.2 | 20 Jul 2012 | stable | Source |
| 3.0.3 | 20 Jul 2012 | stable | Source |
| 3.0.4 | 26 Jul 2012 | stable | Source |
| 3.0.5 | 1 Aug 2012 | stable | Source |
| 3.0.6 | 17 Aug 2012 | stable | Source |
| 3.0.7 | 24 Aug 2012 | stable | Source |
| 3.0.14 | 8 Feb 2013 | stable | Source |
| 3.0.15 | 11 Feb 2013 | stable | Source |
| 3.0.16 | 8 Mar 2013 | stable | Source |
| 3.0.17 | 22 Mar 2013 | stable | Source |
| 3.0.18 | 12 Apr 2013 | stable | Source |
| 3.0.19 | 17 Apr 2013 | stable | Source |
| 3.0.20 | 28 Jun 2013 | stable | Source |
| 3.0.21 | 5 Jul 2013 | stable | Source |
| 3.0.22 | 16 Aug 2013 | stable | Source |
| 3.0.23 | 2 Sept 2013 | stable | Source |
| 3.0.24 | 11 Oct 2013 | stable | Source |
| 3.0.8 | 29 Aug 2012 | stable | Source |
Release activity
- Total releases
- 54
- Last 30 days
- 0
- Last 90 days
- 0
- Avg. interval
- ~48 days
- Most recent
- 31 Aug 2012
Should I use this version?
Suitable for new deployments
Celery 3 is currently supported (standard support).
Version comparison
Compact comparison against the nearest relevant release lines.
Compatibility
Evidence-backed compatibility results involving Celery 3. Only combinations CompatHub can evaluate from upstream sources are listed.
Sources
Where this information comes from.
Lifecycle sources
- Celery PyPI releasesfirst party · high confidence
Official source: https://pypi.org/project/celery/
Last verified 2 Sept 2026
- OSV.devfirst party
Official source: https://osv.dev
Verification time not recorded
- NVD (NIST)first party
Official source: https://nvd.nist.gov
Verification time not recorded
- CISA Known Exploited Vulnerabilitiesfirst party
Official source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Verification time not recorded
Release sources
- Celery PyPI releasesfirst party · high confidence
Official source: https://pypi.org/project/celery/
Last verified 2 Sept 2026
Data coverage
Last checked = last successful upstream check. Latest source update = when upstream content last changed.
- Releases tracked
- 54
- Lifecycle periods
- 1
- EOL
- Not officially published
- Provenance records
- 2
- Data last checked
- 2 Sept 2026
- Latest source update
- 2 Sept 2026
EOL: Not officially published
