celery vulnerabilities
Distributed Task Queue.
- Registry
- PyPI
- Latest
- 5.7.0
- License
- BSD-3-Clause
2 known advisories
The latest version, 5.7.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
pip install 'celery>=5.7.0'Is your project on an affected celery?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for celery
Celery local privilege escalation vulnerability
- Affected
- >=2.1.0 <2.2.8 · >=2.3.0 <2.3.4 · >=2.4.0 <2.4.4
- Fixed in
- 2.2.8, 2.3.4, 2.4.4
OS Command Injection in celery
- Affected
- <5.2.2
- Fixed in
- 5.2.2
Is your celery version vulnerable?
- celery 5.7No known advisories in 5.7.0
- celery 5.6No known advisories in 5.6.3
- celery 5.5No known advisories in 5.5.3
- celery 5.4No known advisories in 5.4.0
- celery 5.3No known advisories in 5.3.6
- celery 5.2No known advisories in 5.2.7
- celery 4.41 advisory in 4.4.7
- celery 4.31 advisory in 4.3.1
- celery 4.21 advisory in 4.2.2
- celery 4.11 advisory in 4.1.1
- celery 4.01 advisory in 4.0.2
- celery 3.11 advisory in 3.1.26
- celery 3.01 advisory in 3.0.25
Which of your client projects still run an old celery?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.