Skip to main content
Mallory
CriticalVulnerability

CVE-2026-96891: Out-of-Bounds Write in D-Link DIR-825 rp-l2tp

Published Sep 24, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v4
EPSS0.65%52nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
D-Link
IdentifiersCVE-2026-96891CWE-787 · Out-of-bounds Write

CVE-2026-96891 is a critical remotely reachable out-of-bounds write in D-Link DIR-825 firmware 3.00b32. The flaw affects the rp-l2tp component's tunnel_set_params function, which insufficiently bounds attacker-controlled peer_hostname data. A crafted L2TP control-channel request can corrupt memory outside the intended buffer.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can corrupt router memory, causing a crash or denial of service. Depending on memory layout and deployed mitigations, the memory corruption may be exploitable for arbitrary code execution, potentially resulting in complete compromise of the router and high confidentiality, integrity, and availability impact.

Mitigation

If you can’t patch tonight, do this now.

Disable L2TP where it is not operationally required. Restrict access to L2TP and router administration services to trusted networks, block internet-originated L2TP traffic, and isolate affected devices on restricted network segments. Monitor affected routers for unexplained reboots, crashes, configuration changes, anomalous outbound traffic, and unexpected processes or services.

Remediation

Patch, then assume compromise.

No fixed firmware release is identified for the affected DIR-825 firmware. Replace affected end-of-life DIR-825 devices with vendor-supported hardware. If a vendor-provided fixed firmware becomes available, apply it after validating the applicable hardware revision and firmware version.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
D-LinkDir-825hardware
FAQ

Frequently asked questions

Is CVE-2026-96891 exploited in the wild?
As of Sep 27, 2026, Mallory has no reports of CVE-2026-96891 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-96891?
As of Sep 27, 2026, Mallory has found no public exploit for CVE-2026-96891.
Is there a patch for CVE-2026-96891?
No fixed firmware release is identified for the affected DIR-825 firmware. Replace affected end-of-life DIR-825 devices with vendor-supported hardware.
What products are affected by CVE-2026-96891?
D-Link Dir-825.
How severe is CVE-2026-96891?
CVE-2026-96891 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 0.65% (52nd percentile) as of Sep 27, 2026.
Activity feed

Recent activity

10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.