Quick answers
- Is CVE-2026-37071 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-37071 being exploited in the wild.
- How severe is CVE-2026-37071?
- Critical severity, with a CVSS score of 9.8, published 27 August 2026.
- Which products and versions are affected?
- Veno File Manager Project 4.4.9.
- Is there a fix for CVE-2026-37071?
- 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-37071 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-37071?
- Check whether you run Veno File Manager Project 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 the Actions::renameFile() function, which fails to properly validate or restrict which files can be renamed. An authenticated attacker with 'rename' permission can send a specially crafted POST request to the rename endpoint, targeting the application's configuration file. By renaming this critical file, the attacker triggers a configuration rebuild that resets the super administrator account credentials to default values. This is a post-authentication privilege escalation attack that requires only basic 'rename' file permissions, not administrative access.
Affected products
- Veno File Manager Project 4.4.9
Timeline
- 2026-08-27: disclosed
- other: CVE-2026-37071 assigned