Quick answers
- Is CVE-2026-92570 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92570 being exploited in the wild.
- How severe is CVE-2026-92570?
- Medium severity, with a CVSS score of 6.5, published 16 September 2026.
- Which products and versions are affected?
- Yogeshojha reNgine through 2.2.0.
- Is there a fix for CVE-2026-92570?
- 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-92570 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-92570?
- 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 GetFileContents API endpoint in reNgine through version 2.2.0 fails to enforce role-based access controls, allowing any authenticated user to read arbitrary bundled recon tool configuration files. The vulnerability is a missing authorization check (CWE-639) rather than an authentication bypass—the endpoint verifies the user is logged in but does not validate their privilege level before granting file access. Attack preconditions include valid authentication credentials (any user account, including low-privilege Auditor roles). An attacker can query the endpoint without proper permission checks to extract files containing API keys for multiple third-party reconnaissance services. A patch or update to version 2.2.1 or later is expected to address this by implementing proper role-based authorization.
Affected products
- yogeshojha reNgine through 2.2.0
Timeline
- 2026-09-16: disclosed