Skip to main content

Technology: redis

IDTitleDescriptionCategoryTechnologyTags
CRE-2025-0058
Medium
Impact: 7/10
Mitigation: 4/10
Celery Worker Stops Consuming Tasks After Redis Restart
  • When Redis is restarted, Celery workers using Redis as a broker may stop consuming tasks without exiting or logging a fatal error.
  • Although Celery Beat continues to publish tasks successfully, the worker remains in a broken state until manually restarted.
  • This results in a silent backlog of scheduled but unprocessed tasks.
Task Management ProblemsredisCelerySilent FailureRedisKombu
CRE-2025-0072
Critical
Impact: 10/10
Mitigation: 7/10
Redis Out-Of-Memory → Persistence Crash → Replica/ACL Write Failures
Detects a cascade of critical Redis failure modes in a single session:
  • Redis refuses writes when maxmemory is exceeded (OOM).
  • RDB snapshot (BGSAVE) fails (MISCONF) due to simulated full-disk.
  • Replica refuses writes (READONLY).
  • ACL denies a write (NOPERM).
In-Memory Database ProblemsredisRedisOut of MemoryPersistenceRDBMISCONFREADONLYACLSecurity