# CVE-2026-92570: reNgine through 2.2.0 Unauthorized Configuration File Read

> Low-privilege users can read sensitive configuration files containing third-party API keys due to missing authorization checks in the GetFileContents endpoint.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-29ch-4262-w3fr

## What is CVE-2026-92570?

CVE-2026-92570 is a high-severity missing authorization vulnerability in yogeshojha rengine, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-92570 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92570 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92570 is a high-severity missing authorization vulnerability in yogeshojha rengine, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92570 exists.

Affected product: yogeshojha rengine. 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-92570/ (Markdown: https://insights.sbomify.com/CVE-2026-92570/index.md)
```

## Sources

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

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