# CVE-2026-71912: DrayTek VigorAP Multiple Models Buffer Overflow via apautotest

> Remote attackers with admin credentials can trigger a buffer overflow in DrayTek VigorAP devices, leading to denial of service or arbitrary code execution.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-79qv-wp74-hqv7

## What is CVE-2026-71912?

CVE-2026-71912 is a high-severity memory corruption vulnerability in DrayTek Corporation VigorAP 1060C, published on 24 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple DrayTek VigorAP models contain a buffer overflow vulnerability in the apautotest function. The vulnerability is caused by missing length checks during memory copy operations involving the CMD6 field. A remote attacker can trigger this vulnerability via crafted input, causing a denial of service or potentially executing arbitrary commands. Exploitation requires valid administrative credentials for the device's web management interface.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2026-71912 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71912 is a high-severity memory corruption vulnerability in DrayTek Corporation VigorAP 1060C, published on 24 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71912 in the wild and no public exploit code.

Affected product: DrayTek Corporation VigorAP 1060C. 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-71912/ (Markdown: https://insights.sbomify.com/CVE-2026-71912/index.md)
```

## Sources

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

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