# CVE-2026-96891: D-Link DIR-825 rp-l2tp tunnel.c tunnel_set_params out-of-bounds write

> Remote attackers can trigger an out-of-bounds write in the rp-l2tp component of D-Link DIR-825 routers, potentially leading to arbitrary code execution.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-3hcq-2p28-7753

## What is CVE-2026-96891?

CVE-2026-96891 is a critical memory corruption vulnerability in D-Link DIR-825, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in D-Link DIR-825 3.00b32. Affected is the function tunnel_set_params of the file tunnel.c of the component rp-l2tp. The manipulation of the argument peer_hostname  leads to out-of-bounds write. The attack may be initiated remotely.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-96891 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96891 is a critical memory corruption vulnerability in D-Link DIR-825, published on 24 Sep 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-96891 in the wild and no public exploit code.

Affected product: D-Link DIR-825. 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-96891/ (Markdown: https://insights.sbomify.com/CVE-2026-96891/index.md)
```

## Sources

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

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