# CVE-2026-79426: Path traversal in n/a

> Authenticated attackers can delete arbitrary files on the server via a crafted POST request in the video data save component.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-r4hr-pfjj-9xhg

## What is CVE-2026-79426?

CVE-2026-79426 is a high-severity path traversal vulnerability in n/a, published on 4 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An arbitrary file deletion vulnerability in the /adminapi/file/video_data_save component of CRMEB v6.0.0 allows authenticated attackers to delete arbitrary files via crafted POST request.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-79426 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79426 is a high-severity path traversal vulnerability in n/a, published on 4 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79426 exists.

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-79426/ (Markdown: https://insights.sbomify.com/CVE-2026-79426/index.md)
```

## Sources

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

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