rConfig Core
rConfig Core 8.0.0 before 8.2.19 and rConfig Pro before 8.4.1 RCE via Unauthenticated Redis Queue Poisoning
rConfig 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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 8.0.0, < 8.2.19
Fixed in 8.2.19
- < 8.4.1
Fixed in 8.4.1
Mitigation
Upgrade rConfig Core to 8.2.19 or later.
Upgrade rConfig Pro to 8.4.1 or later.
References
- Patch github.com/rconfig/rconfig/releases/tag/core-8…
- Vendor advisory rconfig.com/security-advisories
Timeline
Days relative to CVE publicationFirst public PoC 1.7 days after publication; not in CISA KEV. First PoC: googlesky/CVE-2026-124079 (created 11 Nov 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| googlesky/CVE-2026-124079 | 11 Nov 2026 +1.7 d | 14 Nov 2026 | 0 | PoC
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.