Deserialization flaw in rConfig Core and Pro allows remote code execution
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-502.
Summary
rConfig Core from 8.0.0 before 8.2.19 and rConfig Pro before 8.4.1 contain a deserialization flaw (CWE-502) in the Laravel Horizon queue handling. Unauthenticated network attackers can push a crafted serialized job onto the Redis-backed queue, which runs without authentication in affected deployments, and execute arbitrary code. Attackers can also write a persistent web shell into the web-served storage directory and read database credentials, stored device credentials and API tokens. Where Redis is not directly reachable, authenticated attackers can deliver the payload by configuring a device target that points at the rConfig server's loopback address.
Written with Claude Haiku 5.5 from the sources below · 2026-11-09
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade rConfig Core to version 8.2.19 and rConfig Pro to version 8.4.1. The sources list no fixed version for rConfig Core earlier than 8.2.19 or rConfig Pro earlier than 8.4.1.
Written with Claude Haiku 5.5 from the sources below · 2026-11-09
- Fix · CNA rConfig Core (rConfig) Fixed in 8.2.19
- Fix · CNA rConfig Pro (rConfig) Fixed in 8.4.1
Timeline
- 2026-11-09 Threatist record created from CVE-2026-124079
- 2026-11-09 Alias added: GHSA-chv8-5vwm-w6cj
- 2026-11-14 CISA SSVC decision points changed
References
Patch 1
Advisory 1
More rConfig vulnerabilities
- TI-2020-08234 Command injection in rConfig lets remote attackers run OS commands KEVCVSS 3.1HIGH 8.8
- TI-2020-08233 An issue was discovered in rConfig through 3.9.4. CVSS 3.1CRITICAL 9.8
- TI-2019-12460 An issue was discovered in rConfig 3.9.2. CVSS 3.1CRITICAL 9.8
- TI-2020-08465 rConfig 3.9.4 and previous versions has unauthenticated compliancepolicies.inc.php SQL… CVSS 3.1CRITICAL 9.8
- TI-2020-08761 rConfig before 3.9.5 allows command injection by sending a crafted GET request to… CVSS 3.1CRITICAL 9.8
- TI-2020-10700 lib/crud/userprocess.php in rConfig 3.9.x before 3.9.7 has an authentication bypass… CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-124079 · CVE Program
- CVE-2026-124079 · NVD
- FIRST EPSS
- GHSA-chv8-5vwm-w6cj · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences