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

> An authenticated administrator can delete arbitrary files in the application directory by manipulating upload filenames, leading to data loss or denial of service.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-52c3-83c9-5h54

## What is CVE-2026-88621?

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

### Official description

OneNav v1.2.4 contains an authenticated arbitrary file deletion vulnerability in the Api::upload() method in class/Api.php. An authenticated administrator can submit a non-HTML upload filename matching an existing file in the application's working directory. The application passes the user-controlled filename to unlink() when rejecting the upload, potentially causing file deletion and denial of service.

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference)

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


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

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

## Is CVE-2026-88621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88621 is a low-severity path traversal vulnerability in n/a, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-88621 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-88621/ (Markdown: https://insights.sbomify.com/CVE-2026-88621/index.md)
```

## Sources

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

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