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

> A remote attacker can exploit a directory traversal flaw in the IK-Q3000 router to execute arbitrary code on the device.

- **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:** 13 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-rcp7-qh7p-59r7

## What is CVE-2026-78799?

CVE-2026-78799 is a critical path traversal vulnerability in n/a, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory Traversal vulnerability in Quanxun Huiju Network Technology (Beijing) Co., Ltd IK-Q3000 Enterprise-grade Wi-Fi 6 wireless router Enterprise Edition: <= iKuai8_3.7.23_Enterprise Build 202606021825 - Free Edition: <= iKuai 8_4.0.304-beta allows a remote attacker to execute arbitrary code.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-78799 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78799 is a critical path traversal vulnerability in n/a, published on 13 Oct 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-78799 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-78799/ (Markdown: https://insights.sbomify.com/CVE-2026-78799/index.md)
```

## Sources

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

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