pypi package report

Is celery safe?

2 known vulnerabilities, worst severity HIGH.

// reach

43 direct dependencies

11 carry known advisories, worst CRITICAL

92 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade
// ai model usage

No published models are known to use this package.


cvss
7.5
high

CVSS v3.1 base score out of 10

epss
3.6%
medium

chance of exploitation in 30 days, 90th percentile of all CVEs

xyz score
4.7
medium

CyberXYZ composite out of 10

fig. 01 — GHSA-q4xr-rc97-m4xx, the advisory selected below

// 2 advisories

GHSA-q4xr-rc97-m4xx

HIGHGitHub ratingCVE-2021-23727

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 to, or somehow manipulate the metadata within a celery backend, they could trigger a stored command injection vulnerability and potentially gain further access to the system.

// cvss v3.1 vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Checked 2026-11-06 at 22:03 UTC. The most recent advisory here was published 2022-05-17. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.