# CVE-2026-37071: Privilege escalation in n/a

> An authenticated attacker can rename the configuration file to reset admin credentials, allowing them to take over the super administrator account.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-g5hf-q3px-mccp

## What is CVE-2026-37071?

CVE-2026-37071 is a critical vulnerability in n/a, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Arbitrary File Rename Leading to Privilege Escalation in Actions::renameFile() function in Veno File Manager Project 4.4.9 allows an authenticated attacker with 'reanme' permission to take over the super administrator account via a specially crafted POST request to the affected endpoint renaming the application configuration file and triggering a rebuild of configuration and resetting super administrator credentials to default values.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-37071 being exploited?

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

Public exploit code:

- Arbitrary File Rename Leading to Privilege Escalation in Actions::renameFile() function in Veno File Manager Project 4.4.9 allows an authenticated attacker with 'reanme' permission to take over the super administrator account via a specially crafted POST request. (github_poc): https://github.com/jfs-jfs/CVE-2026-37071

## Fix prompt for AI coding agents

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

What it is: CVE-2026-37071 is a critical vulnerability in n/a, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-37071 in the wild and no public exploit code.

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

## Sources

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

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