# CVE-2026-113392: DrayTek Vigor2960 Apmupload mainfunction.cgi path traversal


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-3r48-3g8f-54w9

## What is CVE-2026-113392?

CVE-2026-113392 is a medium-severity vulnerability in DrayTek Vigor2960, published on 20 Oct 2026. 

### Official description

A vulnerability was found in DrayTek Vigor2960 1.5.1.6 Revision 8218. This vulnerability affects unknown code of the file /cgi-bin/mainfunction.cgi of the component Apmupload. Performing a manipulation of the argument action results in path traversal. The attack is possible to be carried out remotely. The exploit has been made public and could be used. Upgrading to version 1.5.1.7 is able to resolve this issue. Upgrading the affected component is advised. The vendor explains: "2960 1.5.1.7 has corrected many security issues. And 2960 is EoS with limited support, only major issues would be reviewed(e.g. unauthenticated vuln.)". This vulnerability only affects products that are no longer supported by the maintainer.

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

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


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

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

## Is CVE-2026-113392 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113392 is a medium-severity vulnerability in DrayTek Vigor2960, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113392 exists.

Affected product: DrayTek Vigor2960. 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-113392/ (Markdown: https://insights.sbomify.com/CVE-2026-113392/index.md)
```

## Sources

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

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