Quick answers
- Is CVE-2026-104584 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104584 being exploited in the wild.
- How severe is CVE-2026-104584?
- Informational severity, published 13 October 2026.
- Which products and versions are affected?
- Yogeshojha reNgine up to v2.2.0 and master branch (commit de4199222cca5618f1255930ce78987e47d43a99).
- Is there a fix for CVE-2026-104584?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-104584 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104584?
- Check whether you run Yogeshojha reNgine at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in web/reNgine/tasks.py (fetch_url and dir_file_fuzz functions) where custom_headers values are concatenated directly into shell commands without sanitization. An authenticated attacker can inject shell metacharacters via the custom_headers scan configuration field to escape quotes and execute arbitrary OS commands. The injected commands run as root within the Celery worker container.
Affected products
- yogeshojha reNgine up to v2.2.0 and master branch (commit de4199222cca5618f1255930ce78987e47d43a99)
Timeline
- 2026-10-13: disclosed