CVE-2026-124079 · Vendor
NO FIX YET · SEE WHAT TO DO
rConfig Core and Pro unserialize jobs pushed onto a Redis-backed Laravel Horizon queue without class restrictions. An unauthenticated network attacker can run PHP and operating system commands as the queue worker, plant a web shell, and read database credentials, device credentials and API tokens.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Deployments of rConfig Core 8.0.0 before 8.2.19 and rConfig Pro before 8.4.1 are exposed. The danger is worst where the Redis queue backing Laravel Horizon is reachable without authentication from the network; where Redis is not directly reachable, an authenticated user who can configure a device target pointing at the server's loopback address can still deliver the payload. Systems on current versions or without this rConfig product can skip it.
Not affected if fixed-version, redis-not-reachable
Who cares laravel, php, rconfig, redis, self-hosted
redis-cli -h <host> pingstorage/app/public8.2.19 or later8.4.1 or laterrConfig Core 8.0.0 before 8.2.19 and rConfig Pro before 8.4.1 contain a deserialization of untrusted data vulnerability that allows unauthenticated network attackers to execute arbitrary code by pushing a crafted serialized job onto the Redis-backed Laravel Horizon queue, which runs without authentication in affected deployments. Laravel's CallQueuedHandler unserializes the job without class restrictions, allowing attackers to instantiate the existing App\Jobs\TaskDownloadRun class and invoke an attacker-controlled Artisan command. Attackers can leverage the bundled laravel/tinker package to execute arbitrary PHP and operating system commands as the queue worker's user, write a persistent web shell into the web-served storage/app/public directory, and read database credentials, stored device credentials, and API tokens. Where Redis is not directly reachable, authenticated attackers can deliver the payload through the application by configuring a device target that points at the rConfig server's loopback address.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.