# CVE-2026-37067: Missing authorization in n/a

> An unauthenticated attacker can extract all application logs from a specific date via a crafted POST request due to incorrect access control.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 28 Aug 2026
- **Also known as:** GHSA-h3cw-hjxp-gp73

## What is CVE-2026-37067?

CVE-2026-37067 is a medium-severity missing authorization 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

Incorrect access control in /vfm-admin/admin-panel/view/save-cvs.php in Veno File Manager Project 4.4.9 allows an unauthenticated attacker to extract all application logs from a desired date forwards via a specially crafted POST request.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-37067 being exploited?

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

Public exploit code:

- Incorrect access control in /vfm-admin/admin-panel/view/save-cvs.php in Veno File Manager Project 4.4.9 allows an unauthenticated attacker to extract all application logs from a desired date forwards via a specially crafted POST request. (github_poc): https://github.com/jfs-jfs/CVE-2026-37067

## Fix prompt for AI coding agents

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

What it is: CVE-2026-37067 is a medium-severity missing authorization 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-37067 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-37067/ (Markdown: https://insights.sbomify.com/CVE-2026-37067/index.md)
```

## Sources

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

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