rConfig Core 8.0.0 before 8.2.19 and rConfig Pro before 8.4.1 RCE via Unauthenticated Redis Queue Poisoning
Affects rConfig Core 8.0.0 before 8.2.19 and rConfig Pro before 8.4.1 where the Redis-backed Laravel Horizon queue runs without authentication. Core fix: upgrade to 8.2.20 or later.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in rConfig Core 8.2.19 · rConfig Pro 8.4.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: rConfig Core 8.2.19 · rConfig Pro 8.4.1.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
rConfig Core and rConfig Pro releases before their fixed versions contain a deserialization flaw that lets an attacker remotely, without logging in, run arbitrary code on the server by pushing a crafted job onto its Redis-backed Laravel Horizon queue. Successful exploitation can also expose database credentials, stored device credentials, and API tokens.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: rConfig Core 8.2.19 · rConfig Pro 8.4.1.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- rConfig rConfig Core
From 8.0.0 · fixed in 8.2.19
- rConfig rConfig Pro
fixed in 8.4.1
Evidence 3
- Advisory
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124079
Is CVE-2026-124079 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A deserialization of untrusted data flaw lets unauthenticated network attackers run arbitrary code as the queue worker's user. The impact includes writing a persistent web shell and reading database credentials, stored device credentials and API tokens.Source: vulncheck.com, rconfig.com
Which versions are affected by CVE-2026-124079?
rConfig Core: from 8.0.0 before 8.2.19. rConfig Pro: before 8.4.1.Source: cve.now feed data
Am I affected, and how do I check?
rConfig Core 8.0.0 before 8.2.19 and rConfig Pro before 8.4.1 are affected. The main exposure is a Redis-backed Laravel Horizon queue that runs without authentication; a device target pointing at the rConfig server's loopback address is listed as an alternative path when Redis is not directly reachable. Check your installed version against these ranges and whether the queue requires authentication.Source: vulncheck.com, rconfig.com
How do I fix CVE-2026-124079?
Upgrade rConfig Core to 8.2.20 or later. Upgrade rConfig Pro to 8.4.1 or later, the first fixed version listed for Pro. No workaround is listed in the facts.Source: vulncheck.com, rconfig.com