# CVE-2026-124079: rConfig Core 8.0.0 before 8.2.19 and rConfig Pro before 8.4.1 RCE via Unauthenticated Redis Queue Poisoning


- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-chv8-5vwm-w6cj

## What is CVE-2026-124079?

CVE-2026-124079 is a critical vulnerability in rConfig Core, published on 9 Nov 2026. 

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-124079?


## How do I fix CVE-2026-124079?

No fix has been published for CVE-2026-124079 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124079 being exploited?

There is no known exploitation of CVE-2026-124079 in the wild and no public exploit code.

Public exploit code:

- PoC for CVE-2026-124079 — unauthenticated RCE in rConfig Core <=8.2.18 / Pro <8.4.1 via Redis-backed Laravel Horizon queue poisoning (CWE-502). Includes a differential environment (8.2.17 vulnerable / 8.2.18 partially patched / 8.2.19 fixed) and the full exploit chain. (github_poc): https://github.com/googlesky/CVE-2026-124079

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124079 and fix it if it is affected.

What it is: CVE-2026-124079 is a critical vulnerability in rConfig Core, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124079 in the wild and no public exploit code.

Affected product: rConfig Core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124079/ (Markdown: https://insights.sbomify.com/CVE-2026-124079/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124079
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124079
- OSV: https://osv.dev/vulnerability/CVE-2026-124079

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124079/
Summaries are generated and may contain mistakes; the official description above is the record.