celery
PyPI2 known CVEs affecting this package
Aggregated from OSV, GitHub Security Advisories, NVD, and vendor advisories. Each CVE links to its full detail page with vendor advisories, patches, fixed versions, and remediation guidance.
CVEs affecting celerypage 1 of 1
- CVE-2011-4356NONECVSS 0.0✓ Fixed in 2.4.42011-12-05
vulnerable: 2.1.0 ... 2.4.3 (21 versions)
Celery 2.1 and 2.2 before 2.2.8, 2.3 before 2.3.4, and 2.4 before 2.4.4 changes the effective id but not the real id during processing of the --uid and --gid arguments to celerybeat, celeryd_detach, celeryd-multi, and celeryev, which allow…
- CVE-2021-23727HIGHCVSS 7.5EG 7.5✓ Fixed in 5.2.22021-12-29
vulnerable: 0.1.10 ... 5.2.1 (184 versions)
This affects the package celery before 5.2.2. It by default trusts the messages and metadata stored in backends (result stores). When reading task metadata from the backend, the data is deserialized. Given that an attacker can gain access …
Check whether celery is used in your infrastructure
EchelonGraph scans your cloud and SBOMs to map every package to your actual deployments. See blast radius for celery CVEs against the assets you own.
Start Free Scan →