Skip to content

Hardening Redis for rConfig

rConfig’s job queue lives in Redis, and Horizon runs every job it finds there. Access to Redis is access to the workers, which is how CVE-2026-124079 escalated. These settings follow Redis’s own security guidance.

One command sets a password in Redis and in .env together, and restarts the workers (redis.auth):

Terminal window
cd /var/www/html/rconfig8
php artisan rconfig:redis-secure

See Redis Authentication for rotation and troubleshooting.

/etc/redis/redis.conf or /etc/redis.conf. Restart Redis afterwards.

# Loopback only, with protected mode as a second layer (redis.bind)
bind 127.0.0.1 -::1
protected-mode yes
# Never silently drop queued jobs under memory pressure (redis.persistence)
maxmemory-policy noeviction
appendonly yes

A remote Redis needs TLS: REDIS_SCHEME=tls in .env (redis.tls_remote).

Horizon, the scheduler and the SNMP trap receiver must never run as root (runtime.worker_user). Check with:

Terminal window
sudo php artisan rconfig:security-check --only=runtime.worker_user

See Worker Privilege.

Standards: Redis security guidance (requirepass, bind, protected-mode), NIST SP 800-53 AC-3, AC-6, IA-2, SC-7.