Skip to content
Fencer Intel
medium 6.9

CVE-2011-4356 json

Celery local privilege escalation vulnerability

published 2011-12-05 14 y ago modified 2026-06-16 4 mo ago also GHSA-rpc6-h455-3rx5 , PYSEC-2011-17 , EUVD-2011-0002

cvss
6.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits
0
none known

Summary

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 allows local users to gain privileges via vectors involving crafted code that is executed by the worker process.

Patch / fix

  • pypi celery 2.2.8, 2.3.4, 2.4.4
  • celery Debian 14, Debian 13, Debian 12 2.4.6-1

debian advisories DEBIAN-CVE-2011-4356

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-4356 updated cvss 6.9

python-celery: Privilege escalation due improper sanitization of --uid and --gid arguments in certain tools (CELERYSA-0001)

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.9 AV:L/AC:M/Au:N/C:C/I:C/A:C

Affected packages

ecosystem package affected fixed in
pypi celery
>=2.1.0, <2.2.8
>=2.3.0, <2.3.4
>=2.4.0, <2.4.4
>=2.1, <2.2.8
>=2.3, <2.3.4
>=2.4, <2.4.4
2.2.8
2.3.4
2.4.4

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-269 Improper Privilege Management

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.