Critical
CVE-2026-124079: rConfig RCE via Unauthenticated Redis Queue
Inttelio Threat Feeds ·
CVE-2026-124079 is a critical deserialization flaw (CWE-502, CVSS 3.1 score 9.8) in rConfig Core and rConfig Pro, a network device configuration management tool. In affected deployments, the Redis-backed Laravel Horizon job queue runs without authentication, so an attacker who can reach Redis can push a crafted job that executes arbitrary PHP and operating system commands on the rConfig server. The issue is fixed in rConfig Core 8.2.19 and rConfig Pro 8.4.1.
| CVE | CVE-2026-124079 |
|---|---|
| CVSS v3.1 | 9.8 CRITICAL |
| Weakness | CWE-502 |
| Exploited in the wild | Not listed in CISA KEV |
| Published | November 9, 2026 |
Who is affected
Organizations running rConfig Core 8.0.0 up to but not including 8.2.19, or rConfig Pro versions before 8.4.1. The source data does not state the lowest affected rConfig Pro version; check the rConfig security advisories page for details. Exposure is highest where the Redis service used by rConfig's Laravel Horizon queue is reachable over the network without authentication. Deployments where Redis is not directly reachable are still at risk from authenticated rConfig users, who can deliver the payload through the application by configuring a device target that points at the rConfig server's loopback address.
What attackers can do
An unauthenticated attacker with network access to the Redis queue can push a crafted serialized job. Laravel's CallQueuedHandler unserializes it without class restrictions, which lets the attacker instantiate rConfig's existing App\Jobs\TaskDownloadRun class and run an Artisan command of their choosing. Using the bundled laravel/tinker package, the attacker can execute arbitrary PHP and operating system commands as the queue worker's user. According to the description, this can be used to write a persistent web shell into the web-served storage/app/public directory and to read database credentials, stored network device credentials, and API tokens. Because rConfig stores credentials for managed network devices, a compromise could extend beyond the rConfig server itself.
Exploitation status
The source data does not include a CISA Known Exploited Vulnerabilities (KEV) entry, so there is no confirmed report of exploitation in the wild in this data. The CVSS 4.0 exploit maturity field is not defined. The vulnerability was published on 2026-11-09 with a public VulnCheck advisory describing the attack technique, and the attack requires no authentication or user interaction where Redis is reachable, so it should be treated as high priority.
What to do now
- Inventory all rConfig installations and record whether each is Core or Pro and which version it runs.
- Upgrade rConfig Core to 8.2.19 or later and rConfig Pro to 8.4.1 or later, following the vendor release notes and security advisories (github.com/rconfig/rconfig/releases/tag/core-8.2.19 and rconfig.com/security-advisories).
- Until patched, verify that the Redis service used by rConfig is not reachable from untrusted networks and requires authentication; restrict access to the rConfig host only. Consult the vendor advisory for any official mitigation guidance, which is not stated in the source data.
- Review who has authenticated access to rConfig, since authenticated users can deliver the payload even when Redis is not exposed, and remove unnecessary accounts.
- Check for signs of compromise, including unexpected files (especially PHP files or possible web shells) in the storage/app/public directory, unusual queued jobs or Artisan/tinker activity, and unexpected processes run by the queue worker's user.
- If compromise is suspected or Redis was exposed, rotate the rConfig database credentials, all network device credentials stored in rConfig, and rConfig API tokens, and review managed network devices for unauthorized changes.
Frequently asked questions
Which rConfig versions fix CVE-2026-124079?
The flaw affects rConfig Core 8.0.0 before 8.2.19 and rConfig Pro before 8.4.1. Upgrading to rConfig Core 8.2.19 or rConfig Pro 8.4.1 (or later) addresses it, per the vendor release and advisory references.
Does an attacker need a login to exploit CVE-2026-124079?
No, not if the Redis-backed Laravel Horizon queue is reachable, because it runs without authentication in affected deployments. Where Redis is not directly reachable, an authenticated rConfig user can still deliver the payload by configuring a device target that points at the rConfig server's loopback address.
Is CVE-2026-124079 being exploited in the wild?
The source data contains no CISA KEV entry, so there is no confirmed in-the-wild exploitation in this data. Given the critical 9.8 CVSS score, the lack of required authentication, and a public advisory describing the technique, organizations should patch promptly.
Sources
- https://nvd.nist.gov/vuln/detail/CVE-2026-124079
- https://github.com/rconfig/rconfig/releases/tag/core-8.2.19
- https://www.rconfig.com/security-advisories
- https://www.vulncheck.com/advisories/rconfig-core-before-and-rconfig-pro-before-rce-via-unauthenticated-redis-queue-poisoning
This briefing was drafted with AI from the official NVD and CISA records. Always confirm affected versions and fixes in the vendor advisory.
Not sure if you are exposed?
Our penetration testers find exploitable flaws before attackers do, and a vCISO can run your vulnerability program.
Talk to Inttelio