reNgine through 2.2.0 Unauthorized Configuration File Read
Published Sep 16, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
reNgine through 2.2.0 Unauthorized Configuration File Read
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
reNgine through 2.2.0 contains an authorization bypass vulnerability in the GetFileContents API endpoint that allows any authenticated user to read bundled recon tool configuration files. Attackers with low-privilege Auditor roles can access files containing third-party API keys for services like SecurityTrails, Shodan, Censys, VirusTotal, BinaryEdge and Hunter by querying the endpoint without role-based permission checks.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- GitHub advisory ↗
- Source repository ↗
- Source repository ↗
- Source repository ↗
- VulnCheck Advisory: reNgine through 2.2.0 Unauthorized Configuration File Read ↗
Record history
Published Sep 16, 2026 · Last refreshed Nov 3, 2026